From: kbuild test robot <lkp@intel.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: Jan Kara <jack@suse.cz>,
linux-nvdimm@lists.01.org, linux-api@vger.kernel.org,
darrick.wong@oracle.com, Dave Chinner <david@fromorbit.com>,
linux-kernel@vger.kernel.org, linux-xfs@vger.kernel.org,
linux-mm@kvack.org, kbuild-all@01.org, luto@kernel.org,
linux-fsdevel@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
Alexander Viro <viro@zeniv.linux.org.uk>
Subject: Re: [PATCH v4 3/3] fs, xfs: introduce MAP_DIRECT for creating block-map-sealed file ranges
Date: Thu, 17 Aug 2017 16:49:48 +0800 [thread overview]
Message-ID: <201708171637.gudWyG5I%fengguang.wu@intel.com> (raw)
In-Reply-To: <150277754211.23945.458876600578531019.stgit@dwillia2-desk3.amr.corp.intel.com>
Hi Dan,
[auto build test ERROR on linus/master]
[also build test ERROR on v4.13-rc5 next-20170816]
[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/Dan-Williams/fs-xfs-introduce-S_IOMAP_SEALED/20170817-114711
config: xtensa-allmodconfig (attached as .config)
compiler: xtensa-linux-gcc (GCC) 4.9.0
reproduce:
wget https://raw.githubusercontent.com/01org/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
make.cross ARCH=xtensa
All error/warnings (new ones prefixed by >>):
mm/mmap.c: In function 'do_mmap':
mm/mmap.c:1391:8: error: 'MAP_VALIDATE' undeclared (first use in this function)
case MAP_VALIDATE:
^
mm/mmap.c:1391:8: note: each undeclared identifier is reported only once for each function it appears in
In file included from mm/mmap.c:17:0:
>> include/linux/mman.h:11:29: error: 'MAP_DIRECT' undeclared (first use in this function)
#define MAP_SUPPORTED_MASK (MAP_DIRECT)
^
>> mm/mmap.c:1392:18: note: in expansion of macro 'MAP_SUPPORTED_MASK'
if (flags & ~(MAP_SUPPORTED_MASK | MAP_VALIDATE))
^
vim +/MAP_DIRECT +11 include/linux/mman.h
9
10 /* the MAP_VALIDATE set of supported flags */
> 11 #define MAP_SUPPORTED_MASK (MAP_DIRECT)
12
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
WARNING: multiple messages have this Message-ID (diff)
From: kbuild test robot <lkp@intel.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: kbuild-all@01.org, darrick.wong@oracle.com,
Jan Kara <jack@suse.cz>,
linux-nvdimm@lists.01.org, linux-api@vger.kernel.org,
Dave Chinner <david@fromorbit.com>,
linux-kernel@vger.kernel.org, linux-xfs@vger.kernel.org,
linux-mm@kvack.org, Jeff Moyer <jmoyer@redhat.com>,
Alexander Viro <viro@zeniv.linux.org.uk>,
luto@kernel.org, linux-fsdevel@vger.kernel.org,
Ross Zwisler <ross.zwisler@linux.intel.com>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH v4 3/3] fs, xfs: introduce MAP_DIRECT for creating block-map-sealed file ranges
Date: Thu, 17 Aug 2017 16:49:48 +0800 [thread overview]
Message-ID: <201708171637.gudWyG5I%fengguang.wu@intel.com> (raw)
In-Reply-To: <150277754211.23945.458876600578531019.stgit@dwillia2-desk3.amr.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1634 bytes --]
Hi Dan,
[auto build test ERROR on linus/master]
[also build test ERROR on v4.13-rc5 next-20170816]
[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/Dan-Williams/fs-xfs-introduce-S_IOMAP_SEALED/20170817-114711
config: xtensa-allmodconfig (attached as .config)
compiler: xtensa-linux-gcc (GCC) 4.9.0
reproduce:
wget https://raw.githubusercontent.com/01org/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
make.cross ARCH=xtensa
All error/warnings (new ones prefixed by >>):
mm/mmap.c: In function 'do_mmap':
mm/mmap.c:1391:8: error: 'MAP_VALIDATE' undeclared (first use in this function)
case MAP_VALIDATE:
^
mm/mmap.c:1391:8: note: each undeclared identifier is reported only once for each function it appears in
In file included from mm/mmap.c:17:0:
>> include/linux/mman.h:11:29: error: 'MAP_DIRECT' undeclared (first use in this function)
#define MAP_SUPPORTED_MASK (MAP_DIRECT)
^
>> mm/mmap.c:1392:18: note: in expansion of macro 'MAP_SUPPORTED_MASK'
if (flags & ~(MAP_SUPPORTED_MASK | MAP_VALIDATE))
^
vim +/MAP_DIRECT +11 include/linux/mman.h
9
10 /* the MAP_VALIDATE set of supported flags */
> 11 #define MAP_SUPPORTED_MASK (MAP_DIRECT)
12
---
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: 50926 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: kbuild test robot <lkp-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: Dan Williams <dan.j.williams-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: Jan Kara <jack-AlSwsSmVLrQ@public.gmane.org>,
linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org,
linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
darrick.wong-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org,
Dave Chinner <david-FqsqvQoI3Ljby3iVrkZq2A@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-xfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org,
kbuild-all-JC7UmRfGjtg@public.gmane.org,
luto-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>,
Alexander Viro
<viro-RmSDqhL/yNMiFSDQTTA3OLVCufUGDwFn@public.gmane.org>
Subject: Re: [PATCH v4 3/3] fs, xfs: introduce MAP_DIRECT for creating block-map-sealed file ranges
Date: Thu, 17 Aug 2017 16:49:48 +0800 [thread overview]
Message-ID: <201708171637.gudWyG5I%fengguang.wu@intel.com> (raw)
In-Reply-To: <150277754211.23945.458876600578531019.stgit-p8uTFz9XbKj2zm6wflaqv1nYeNYlB/vhral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Hi Dan,
[auto build test ERROR on linus/master]
[also build test ERROR on v4.13-rc5 next-20170816]
[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/Dan-Williams/fs-xfs-introduce-S_IOMAP_SEALED/20170817-114711
config: xtensa-allmodconfig (attached as .config)
compiler: xtensa-linux-gcc (GCC) 4.9.0
reproduce:
wget https://raw.githubusercontent.com/01org/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
make.cross ARCH=xtensa
All error/warnings (new ones prefixed by >>):
mm/mmap.c: In function 'do_mmap':
mm/mmap.c:1391:8: error: 'MAP_VALIDATE' undeclared (first use in this function)
case MAP_VALIDATE:
^
mm/mmap.c:1391:8: note: each undeclared identifier is reported only once for each function it appears in
In file included from mm/mmap.c:17:0:
>> include/linux/mman.h:11:29: error: 'MAP_DIRECT' undeclared (first use in this function)
#define MAP_SUPPORTED_MASK (MAP_DIRECT)
^
>> mm/mmap.c:1392:18: note: in expansion of macro 'MAP_SUPPORTED_MASK'
if (flags & ~(MAP_SUPPORTED_MASK | MAP_VALIDATE))
^
vim +/MAP_DIRECT +11 include/linux/mman.h
9
10 /* the MAP_VALIDATE set of supported flags */
> 11 #define MAP_SUPPORTED_MASK (MAP_DIRECT)
12
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
next prev parent reply other threads:[~2017-08-17 8:48 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-15 6:12 [PATCH v4 0/3] MAP_DIRECT and block-map sealed files Dan Williams
2017-08-15 6:12 ` Dan Williams
2017-08-15 6:12 ` Dan Williams
2017-08-15 6:12 ` Dan Williams
2017-08-15 6:12 ` [PATCH v4 1/3] fs, xfs: introduce S_IOMAP_SEALED Dan Williams
2017-08-15 6:12 ` Dan Williams
2017-08-15 6:12 ` Dan Williams
2017-08-15 6:12 ` [PATCH v4 2/3] mm: introduce MAP_VALIDATE a mechanism for adding new mmap flags Dan Williams
2017-08-15 6:12 ` Dan Williams
2017-08-15 6:12 ` Dan Williams
2017-08-15 6:12 ` Dan Williams
2017-08-15 12:27 ` Jan Kara
2017-08-15 12:27 ` Jan Kara
2017-08-15 16:24 ` Dan Williams
2017-08-15 16:24 ` Dan Williams
2017-08-15 16:24 ` Dan Williams
2017-08-15 16:24 ` Dan Williams
2017-09-17 3:44 ` Dan Williams
2017-09-17 3:44 ` Dan Williams
2017-09-17 3:44 ` Dan Williams
2017-09-17 17:39 ` Christoph Hellwig
2017-09-17 17:39 ` Christoph Hellwig
2017-09-17 17:39 ` Christoph Hellwig
2017-09-18 9:31 ` Jan Kara
2017-09-18 9:31 ` Jan Kara
2017-09-18 9:31 ` Jan Kara
2017-09-18 9:31 ` Jan Kara
2017-09-18 15:47 ` Dan Williams
2017-09-18 15:47 ` Dan Williams
2017-09-18 9:26 ` Jan Kara
2017-09-18 9:26 ` Jan Kara
2017-09-18 9:26 ` Jan Kara
2017-08-15 16:28 ` Andy Lutomirski
2017-08-15 16:28 ` Andy Lutomirski
2017-08-15 16:28 ` Andy Lutomirski
2017-08-15 22:31 ` Dan Williams
2017-08-15 22:31 ` Dan Williams
2017-08-17 8:06 ` kbuild test robot
2017-08-17 8:06 ` kbuild test robot
2017-08-15 6:12 ` [PATCH v4 3/3] fs, xfs: introduce MAP_DIRECT for creating block-map-sealed file ranges Dan Williams
2017-08-15 6:12 ` Dan Williams
2017-08-15 6:12 ` Dan Williams
2017-08-15 9:18 ` Kirill A. Shutemov
2017-08-15 9:18 ` Kirill A. Shutemov
2017-08-15 9:18 ` Kirill A. Shutemov
2017-08-15 17:11 ` Dan Williams
2017-08-15 17:11 ` Dan Williams
2017-08-15 17:11 ` Dan Williams
2017-08-16 10:25 ` Kirill A. Shutemov
2017-08-16 10:25 ` Kirill A. Shutemov
2017-08-16 10:25 ` Kirill A. Shutemov
2017-08-15 12:42 ` Jan Kara
2017-08-15 12:42 ` Jan Kara
2017-08-15 12:42 ` Jan Kara
2017-08-15 16:29 ` Dan Williams
2017-08-15 16:29 ` Dan Williams
2017-08-15 16:29 ` Dan Williams
2017-08-15 16:29 ` Dan Williams
2017-08-16 1:15 ` Dan Williams
2017-08-16 1:15 ` Dan Williams
2017-08-16 1:15 ` Dan Williams
2017-08-16 1:15 ` Dan Williams
2017-08-17 8:49 ` kbuild test robot [this message]
2017-08-17 8:49 ` kbuild test robot
2017-08-17 8:49 ` kbuild test robot
2017-08-15 9:01 ` [PATCH v4 0/3] MAP_DIRECT and block-map sealed files Dave Chinner
2017-08-15 9:01 ` Dave Chinner
2017-08-15 9:01 ` Dave Chinner
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=201708171637.gudWyG5I%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=dan.j.williams@intel.com \
--cc=darrick.wong@oracle.com \
--cc=david@fromorbit.com \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=kbuild-all@01.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nvdimm@lists.01.org \
--cc=linux-xfs@vger.kernel.org \
--cc=luto@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.