From: kbuild test robot <lkp@intel.com>
To: Davidlohr Bueso <dave@stgolabs.net>
Cc: kbuild-all@01.org, mingo@kernel.org, peterz@infradead.org,
akpm@linux-foundation.org, jack@suse.cz,
kirill.shutemov@linux.intel.com, mhocko@suse.com,
mgorman@techsingularity.net, dave@stgolabs.net,
linux-kernel@vger.kernel.org, oleg.drokin@intel.com,
andreas.dilger@intel.com, jsimmons@infradead.org,
lustre-devel@lists.lustre.org, Davidlohr Bueso <dbueso@suse.de>
Subject: Re: [PATCH 5/5] staging/lustre: Use generic range rwlock
Date: Thu, 9 Mar 2017 16:56:19 +0800 [thread overview]
Message-ID: <201703091601.TR7uxISO%fengguang.wu@intel.com> (raw)
In-Reply-To: <1488863010-13028-6-git-send-email-dave@stgolabs.net>
[-- Attachment #1: Type: text/plain, Size: 3631 bytes --]
Hi Davidlohr,
[auto build test WARNING on staging/staging-testing]
[also build test WARNING on v4.11-rc1 next-20170309]
[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/Davidlohr-Bueso/locking-Introduce-range-reader-writer-lock/20170309-140444
config: i386-allmodconfig (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All warnings (new ones prefixed by >>):
In file included from drivers/staging/lustre/lustre/llite/../include/lustre/lustre_idl.h:76:0,
from drivers/staging/lustre/lustre/llite/../include/lustre_lib.h:49,
from drivers/staging/lustre/lustre/llite/../include/lustre_dlm.h:47,
from drivers/staging/lustre/lustre/llite/file.c:40:
drivers/staging/lustre/lustre/llite/file.c: In function 'll_file_io_generic':
>> drivers/staging/lustre/lustre/llite/../include/lustre/lustre_user.h:78:20: warning: large integer implicitly truncated to unsigned type [-Woverflow]
#define LUSTRE_EOF 0xffffffffffffffffULL
^
>> drivers/staging/lustre/lustre/llite/file.c:1072:33: note: in expansion of macro 'LUSTRE_EOF'
range_rwlock_init(&range, 0, LUSTRE_EOF);
^~~~~~~~~~
vim +78 drivers/staging/lustre/lustre/llite/../include/lustre/lustre_user.h
23ec6607e9 John L. Hammond 2016-09-18 62 * are co-existing.
23ec6607e9 John L. Hammond 2016-09-18 63 */
23ec6607e9 John L. Hammond 2016-09-18 64 #if __BITS_PER_LONG != 64 || defined(__ARCH_WANT_STAT64)
23ec6607e9 John L. Hammond 2016-09-18 65 typedef struct stat64 lstat_t;
23ec6607e9 John L. Hammond 2016-09-18 66 #define lstat_f lstat64
f0cf21abcc John L. Hammond 2016-10-02 67 #define fstat_f fstat64
f0cf21abcc John L. Hammond 2016-10-02 68 #define fstatat_f fstatat64
23ec6607e9 John L. Hammond 2016-09-18 69 #else
23ec6607e9 John L. Hammond 2016-09-18 70 typedef struct stat lstat_t;
23ec6607e9 John L. Hammond 2016-09-18 71 #define lstat_f lstat
f0cf21abcc John L. Hammond 2016-10-02 72 #define fstat_f fstat
f0cf21abcc John L. Hammond 2016-10-02 73 #define fstatat_f fstatat
23ec6607e9 John L. Hammond 2016-09-18 74 #endif
23ec6607e9 John L. Hammond 2016-09-18 75
23ec6607e9 John L. Hammond 2016-09-18 76 #define HAVE_LOV_USER_MDS_DATA
d7e09d0397 Peng Tao 2013-05-02 77
00c0a6aea0 John L. Hammond 2016-08-16 @78 #define LUSTRE_EOF 0xffffffffffffffffULL
00c0a6aea0 John L. Hammond 2016-08-16 79
d7e09d0397 Peng Tao 2013-05-02 80 /* for statfs() */
d7e09d0397 Peng Tao 2013-05-02 81 #define LL_SUPER_MAGIC 0x0BD00BD0
d7e09d0397 Peng Tao 2013-05-02 82
d7e09d0397 Peng Tao 2013-05-02 83 #ifndef FSFILT_IOC_GETFLAGS
d7e09d0397 Peng Tao 2013-05-02 84 #define FSFILT_IOC_GETFLAGS _IOR('f', 1, long)
d7e09d0397 Peng Tao 2013-05-02 85 #define FSFILT_IOC_SETFLAGS _IOW('f', 2, long)
d7e09d0397 Peng Tao 2013-05-02 86 #define FSFILT_IOC_GETVERSION _IOR('f', 3, long)
:::::: The code at line 78 was first introduced by commit
:::::: 00c0a6aea0d0ab2c11594616244d787ad7bf64dc staging: lustre: uapi: reduce scope of lustre_idl.h
:::::: TO: John L. Hammond <john.hammond@intel.com>
:::::: CC: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
---
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: 59084 bytes --]
next prev parent reply other threads:[~2017-03-09 8:57 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-07 5:03 [PATCH 0/5] locking Introduce range reader/writer lock Davidlohr Bueso
2017-03-07 5:03 ` [PATCH 1/5] locking: " Davidlohr Bueso
2017-03-09 11:03 ` Jan Kara
2017-03-28 10:00 ` Laurent Dufour
2017-03-28 16:39 ` Davidlohr Bueso
2017-03-28 16:58 ` Kirill A. Shutemov
2017-03-29 8:38 ` Laurent Dufour
2017-03-29 15:31 ` Davidlohr Bueso
2017-03-29 15:40 ` Kirill A. Shutemov
2017-03-29 16:10 ` Davidlohr Bueso
2017-04-03 14:19 ` Laurent Dufour
2017-04-03 15:26 ` Davidlohr Bueso
2017-04-03 16:06 ` Jan Kara
2017-04-04 15:31 ` Davidlohr Bueso
2017-03-29 8:56 ` Peter Zijlstra
2017-03-29 15:12 ` Davidlohr Bueso
2017-03-29 8:59 ` Peter Zijlstra
2017-03-29 9:08 ` Peter Zijlstra
2017-03-29 15:05 ` Davidlohr Bueso
2017-03-29 9:11 ` Peter Zijlstra
2017-03-29 9:44 ` Peter Zijlstra
2017-03-29 10:35 ` Peter Zijlstra
2017-03-29 10:49 ` Peter Zijlstra
2017-03-29 15:14 ` Davidlohr Bueso
2017-03-30 14:56 ` Laurent Dufour
2017-03-30 17:13 ` Davidlohr Bueso
2017-03-07 5:03 ` [PATCH 2/5] locking/locktorture: Fix rwsem reader_delay Davidlohr Bueso
2017-03-07 5:03 ` [PATCH 3/5] locking/locktorture: Fix num reader/writer corner cases Davidlohr Bueso
2017-03-07 5:03 ` [PATCH 4/5] locking/locktorture: Support range rwlocks Davidlohr Bueso
2017-03-07 5:03 ` [PATCH 5/5] staging/lustre: Use generic range rwlock Davidlohr Bueso
2017-03-07 6:05 ` Oleg Drokin
2017-03-08 15:02 ` Davidlohr Bueso
2017-03-09 8:56 ` kbuild test robot [this message]
2017-03-09 14:40 ` kbuild test robot
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=201703091601.TR7uxISO%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=andreas.dilger@intel.com \
--cc=dave@stgolabs.net \
--cc=dbueso@suse.de \
--cc=jack@suse.cz \
--cc=jsimmons@infradead.org \
--cc=kbuild-all@01.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lustre-devel@lists.lustre.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@suse.com \
--cc=mingo@kernel.org \
--cc=oleg.drokin@intel.com \
--cc=peterz@infradead.org \
/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
all inboxes | Powered by JetHome®