From: kbuild test robot <lkp@intel.com>
To: Trond Myklebust <trondmy@gmail.com>
Cc: kbuild-all@01.org, "J. Bruce Fields" <bfields@redhat.com>,
linux-nfs@vger.kernel.org
Subject: Re: [PATCH 2/3] nfsd: Support the server resetting the boot verifier
Date: Tue, 27 Aug 2019 15:58:07 +0800 [thread overview]
Message-ID: <201908271554.Ir2c3hxl%lkp@intel.com> (raw)
In-Reply-To: <20190826165021.81075-3-trond.myklebust@hammerspace.com>
[-- Attachment #1: Type: text/plain, Size: 4700 bytes --]
Hi Trond,
I love your patch! Perhaps something to improve:
[auto build test WARNING on nfsd/nfsd-next]
[cannot apply to v5.3-rc6 next-20190826]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Trond-Myklebust/Handling-NFSv3-I-O-errors-in-knfsd/20190827-144324
base: git://linux-nfs.org/~bfields/linux.git nfsd-next
config: sparc64-allmodconfig (attached as .config)
compiler: sparc64-linux-gcc (GCC) 7.4.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
GCC_VERSION=7.4.0 make.cross ARCH=sparc64
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
Note: it may well be a FALSE warning. FWIW you are at least aware of it now.
http://gcc.gnu.org/wiki/Better_Uninitialized_Warnings
All warnings (new ones prefixed by >>):
In file included from include/linux/time.h:6:0,
from include/linux/ktime.h:24,
from include/linux/timer.h:6,
from include/linux/workqueue.h:9,
from include/linux/rhashtable-types.h:15,
from include/linux/ipc.h:7,
from include/uapi/linux/sem.h:5,
from include/linux/sem.h:5,
from include/linux/sched.h:15,
from include/linux/sched/signal.h:7,
from fs/nfsd/nfssvc.c:10:
fs/nfsd/nfssvc.c: In function 'nfsd_copy_boot_verifier':
>> include/linux/seqlock.h:528:13: warning: 'seq' may be used uninitialized in this function [-Wmaybe-uninitialized]
if (!(*seq & 1)) /* Even */
~~~~~~^~~~
fs/nfsd/nfssvc.c:349:6: note: 'seq' was declared here
int seq;
^~~
--
In file included from include/linux/time.h:6:0,
from include/linux/ktime.h:24,
from include/linux/timer.h:6,
from include/linux/workqueue.h:9,
from include/linux/rhashtable-types.h:15,
from include/linux/ipc.h:7,
from include/uapi/linux/sem.h:5,
from include/linux/sem.h:5,
from include/linux/sched.h:15,
from include/linux/sched/signal.h:7,
from fs//nfsd/nfssvc.c:10:
fs//nfsd/nfssvc.c: In function 'nfsd_copy_boot_verifier':
>> include/linux/seqlock.h:528:13: warning: 'seq' may be used uninitialized in this function [-Wmaybe-uninitialized]
if (!(*seq & 1)) /* Even */
~~~~~~^~~~
fs//nfsd/nfssvc.c:349:6: note: 'seq' was declared here
int seq;
^~~
vim +/seq +528 include/linux/seqlock.h
1370e97bb2eb1e Waiman Long 2013-09-12 515
2bc74feba12fbf Al Viro 2013-10-25 516 /**
2bc74feba12fbf Al Viro 2013-10-25 517 * read_seqbegin_or_lock - begin a sequence number check or locking block
2bc74feba12fbf Al Viro 2013-10-25 518 * @lock: sequence lock
2bc74feba12fbf Al Viro 2013-10-25 519 * @seq : sequence number to be checked
2bc74feba12fbf Al Viro 2013-10-25 520 *
2bc74feba12fbf Al Viro 2013-10-25 521 * First try it once optimistically without taking the lock. If that fails,
2bc74feba12fbf Al Viro 2013-10-25 522 * take the lock. The sequence number is also used as a marker for deciding
2bc74feba12fbf Al Viro 2013-10-25 523 * whether to be a reader (even) or writer (odd).
2bc74feba12fbf Al Viro 2013-10-25 524 * N.B. seq must be initialized to an even number to begin with.
2bc74feba12fbf Al Viro 2013-10-25 525 */
2bc74feba12fbf Al Viro 2013-10-25 526 static inline void read_seqbegin_or_lock(seqlock_t *lock, int *seq)
2bc74feba12fbf Al Viro 2013-10-25 527 {
2bc74feba12fbf Al Viro 2013-10-25 @528 if (!(*seq & 1)) /* Even */
2bc74feba12fbf Al Viro 2013-10-25 529 *seq = read_seqbegin(lock);
2bc74feba12fbf Al Viro 2013-10-25 530 else /* Odd */
2bc74feba12fbf Al Viro 2013-10-25 531 read_seqlock_excl(lock);
2bc74feba12fbf Al Viro 2013-10-25 532 }
2bc74feba12fbf Al Viro 2013-10-25 533
:::::: The code at line 528 was first introduced by commit
:::::: 2bc74feba12fbf052ec97aee8624c9f13593a9ac take read_seqbegin_or_lock() and friends to seqlock.h
:::::: TO: Al Viro <viro@zeniv.linux.org.uk>
:::::: CC: Al Viro <viro@zeniv.linux.org.uk>
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 58655 bytes --]
next prev parent reply other threads:[~2019-08-27 7:58 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-26 16:50 [PATCH 0/3] Handling NFSv3 I/O errors in knfsd Trond Myklebust
2019-08-26 16:50 ` [PATCH 1/3] nfsd: nfsd_file cache entries should be per net namespace Trond Myklebust
2019-08-26 16:50 ` [PATCH 2/3] nfsd: Support the server resetting the boot verifier Trond Myklebust
2019-08-26 16:50 ` [PATCH 3/3] nfsd: Don't garbage collect files that might contain write errors Trond Myklebust
2019-08-27 7:58 ` kbuild test robot [this message]
2019-08-26 20:51 ` [PATCH 0/3] Handling NFSv3 I/O errors in knfsd J. Bruce Fields
2019-08-26 21:02 ` Trond Myklebust
2019-08-27 0:48 ` bfields
2019-08-27 0:56 ` Trond Myklebust
2019-08-27 1:13 ` bfields
2019-08-27 1:28 ` Trond Myklebust
2019-08-27 13:59 ` Chuck Lever
2019-08-27 14:53 ` Trond Myklebust
2019-08-27 14:58 ` bfields
2019-08-27 14:59 ` bfields
2019-08-27 15:15 ` Trond Myklebust
2019-08-27 15:20 ` Chuck Lever
2019-08-28 13:48 ` bfields
2019-08-28 13:51 ` Jeff Layton
2019-08-28 13:57 ` Chuck Lever
2019-08-28 14:00 ` J. Bruce Fields
2019-08-28 14:03 ` Chuck Lever
2019-08-28 14:16 ` Jeff Layton
2019-08-28 14:21 ` Chuck Lever
2019-08-28 14:40 ` J. Bruce Fields
2019-08-28 14:48 ` Bruce Fields
2019-08-28 14:50 ` Chuck Lever
2019-08-28 17:07 ` Bruce Fields
2019-08-28 15:09 ` Jeff Layton
2019-08-28 15:12 ` Rick Macklem
2019-08-28 15:37 ` Trond Myklebust
2019-08-28 15:46 ` Bruce Fields
2019-08-27 14:54 ` Bruce Fields
2019-08-27 14:59 ` Trond Myklebust
2019-08-27 15:00 ` bfields
2019-08-27 15:17 ` Jeff Layton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201908271554.Ir2c3hxl%lkp@intel.com \
--to=lkp@intel.com \
--cc=bfields@redhat.com \
--cc=kbuild-all@01.org \
--cc=linux-nfs@vger.kernel.org \
--cc=trondmy@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).