From: kbuild test robot <lkp@intel.com>
To: David Howells <dhowells@redhat.com>
Cc: kbuild-all@01.org, viro@zeniv.linux.org.uk, dhowells@redhat.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
jlayton@redhat.com, mszeredi@redhat.com
Subject: Re: [PATCH] VFS: Differentiate mount flags (MS_*) from internal superblock flags
Date: Sun, 11 Jun 2017 01:15:49 +0800 [thread overview]
Message-ID: <201706110108.06cQbzCU%fengguang.wu@intel.com> (raw)
In-Reply-To: <149702046967.13949.14361137102849681738.stgit@warthog.procyon.org.uk>
[-- Attachment #1: Type: text/plain, Size: 2480 bytes --]
Hi David,
[auto build test ERROR on linus/master]
[also build test ERROR on v4.12-rc4]
[cannot apply to next-20170609]
[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/David-Howells/VFS-Differentiate-mount-flags-MS_-from-internal-superblock-flags/20170611-000825
config: i386-randconfig-x073-06041529 (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 error/warnings (new ones prefixed by >>):
In file included from fs/cifs/connect.c:21:0:
fs/cifs/connect.c: In function 'compare_mount_options':
>> include/linux/fs.h:1266:20: error: expected ')' before numeric constant
#define SB_NOEXEC 8 /* Disallow program execution */
^
>> fs/cifs/cifsglob.h:561:9: note: in expansion of macro 'SB_NOEXEC'
SB_NOEXEC | SB_NOSUID | SB_NODEV)
^~~~~~~~~
>> fs/cifs/connect.c:2883:21: note: in expansion of macro 'CIFS_MS_MASK'
if ((sb->s_flags & CIFS_MS_MASK) != (mnt_data->flags & CIFS_MS_MASK))
^~~~~~~~~~~~
>> include/linux/fs.h:1266:20: error: expected ')' before numeric constant
#define SB_NOEXEC 8 /* Disallow program execution */
^
>> fs/cifs/cifsglob.h:561:9: note: in expansion of macro 'SB_NOEXEC'
SB_NOEXEC | SB_NOSUID | SB_NODEV)
^~~~~~~~~
fs/cifs/connect.c:2883:57: note: in expansion of macro 'CIFS_MS_MASK'
if ((sb->s_flags & CIFS_MS_MASK) != (mnt_data->flags & CIFS_MS_MASK))
^~~~~~~~~~~~
vim +1266 include/linux/fs.h
1260 * sb->s_flags. Note that these mirror the equivalent MS_* flags where
1261 * represented in both.
1262 */
1263 #define SB_RDONLY 1 /* Mount read-only */
1264 #define SB_NOSUID 2 /* Ignore suid and sgid bits */
1265 #define SB_NODEV 4 /* Disallow access to device special files */
> 1266 #define SB_NOEXEC 8 /* Disallow program execution */
1267 #define SB_SYNCHRONOUS 16 /* Writes are synced at once */
1268 #define SB_MANDLOCK 64 /* Allow mandatory locks on an FS */
1269 #define SB_DIRSYNC 128 /* Directory modifications are synchronous */
---
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: 30676 bytes --]
next prev parent reply other threads:[~2017-06-10 17:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-09 15:01 [PATCH] VFS: Differentiate mount flags (MS_*) from internal superblock flags David Howells
2017-06-09 15:33 ` Jeff Layton
2017-06-09 16:04 ` David Howells
2017-06-10 17:15 ` kbuild test robot [this message]
2017-06-14 14:56 ` David Howells
2017-06-10 17:59 ` 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=201706110108.06cQbzCU%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=dhowells@redhat.com \
--cc=jlayton@redhat.com \
--cc=kbuild-all@01.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mszeredi@redhat.com \
--cc=viro@zeniv.linux.org.uk \
/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).