From: kernel test robot <lkp@intel.com>
To: Mikulas Patocka <mpatocka@redhat.com>, Christoph Hellwig <hch@lst.de>
Cc: kbuild-all@lists.01.org, Jens Axboe <axboe@kernel.dk>,
Ming Lei <ming.lei@redhat.com>,
Zdenek Kabelac <zkabelac@redhat.com>,
linux-block@vger.kernel.org, dm-devel@redhat.com,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v3] loop: don't print warnings if the underlying filesystem doesn't support discard
Date: Wed, 13 Oct 2021 10:56:53 +0800 [thread overview]
Message-ID: <202110131010.5v1ptkpj-lkp@intel.com> (raw)
In-Reply-To: <alpine.LRH.2.02.2110121516440.21015@file01.intranet.prod.int.rdu2.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2862 bytes --]
Hi Mikulas,
I love your patch! Yet something to improve:
[auto build test ERROR on axboe-block/for-next]
[also build test ERROR on kdave/for-next ceph-client/for-linus cifs/for-next tytso-ext4/dev jaegeuk-f2fs/dev-test mszeredi-fuse/for-next linus/master v5.15-rc5 next-20211012]
[cannot apply to hch-configfs/for-next gfs2/for-next]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/0day-ci/linux/commits/Mikulas-Patocka/loop-don-t-print-warnings-if-the-underlying-filesystem-doesn-t-support-discard/20211013-042727
base: https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git for-next
config: arc-randconfig-r043-20211012 (attached as .config)
compiler: arc-elf-gcc (GCC) 11.2.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/0day-ci/linux/commit/c381403746bc0dc3eb5db4b157408430febd6ecf
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Mikulas-Patocka/loop-don-t-print-warnings-if-the-underlying-filesystem-doesn-t-support-discard/20211013-042727
git checkout c381403746bc0dc3eb5db4b157408430febd6ecf
# save the attached .config to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=arc SHELL=/bin/bash fs/fuse/ fs/overlayfs/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> fs/overlayfs/file.c:661:38: error: 'FALLOC_FL_SUPPORTED_MASK' undeclared here (not in a function)
661 | .fallocate_supported_flags = FALLOC_FL_SUPPORTED_MASK,
| ^~~~~~~~~~~~~~~~~~~~~~~~
vim +/FALLOC_FL_SUPPORTED_MASK +661 fs/overlayfs/file.c
651
652 const struct file_operations ovl_file_operations = {
653 .open = ovl_open,
654 .release = ovl_release,
655 .llseek = ovl_llseek,
656 .read_iter = ovl_read_iter,
657 .write_iter = ovl_write_iter,
658 .fsync = ovl_fsync,
659 .mmap = ovl_mmap,
660 .fallocate = ovl_fallocate,
> 661 .fallocate_supported_flags = FALLOC_FL_SUPPORTED_MASK,
662 .fadvise = ovl_fadvise,
663 .flush = ovl_flush,
664 .splice_read = generic_file_splice_read,
665 .splice_write = ovl_splice_write,
666
667 .copy_file_range = ovl_copy_file_range,
668 .remap_file_range = ovl_remap_file_range,
669 };
670
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 33898 bytes --]
next prev parent reply other threads:[~2021-10-13 2:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-23 19:48 [PATCH] loop: don't print warnings if the underlying filesystem doesn't support discard Mikulas Patocka
2021-09-24 0:17 ` Ming Lei
2021-09-24 15:58 ` Christoph Hellwig
2021-10-04 13:01 ` Mikulas Patocka
2021-10-12 6:20 ` Christoph Hellwig
2021-10-12 20:25 ` [PATCH v3] " Mikulas Patocka
2021-10-13 2:56 ` kernel test robot [this message]
2021-10-13 5:06 ` kernel test robot
2021-10-13 9:28 ` [PATCH v4] " Mikulas Patocka
2021-10-27 5:02 ` Dave Chinner
2021-10-27 8:28 ` Mikulas Patocka
2021-10-28 4:15 ` 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=202110131010.5v1ptkpj-lkp@intel.com \
--to=lkp@intel.com \
--cc=axboe@kernel.dk \
--cc=dm-devel@redhat.com \
--cc=hch@lst.de \
--cc=kbuild-all@lists.01.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=mpatocka@redhat.com \
--cc=zkabelac@redhat.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