From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [RFC PATCH 5/5] ovl: impement containerized syncfs for overlayfs
Date: Sun, 11 Oct 2020 11:10:23 +0800 [thread overview]
Message-ID: <202010111114.J7fa41SK-lkp@intel.com> (raw)
In-Reply-To: <20201010142355.741645-6-cgxu519@mykernel.net>
[-- Attachment #1: Type: text/plain, Size: 3806 bytes --]
Hi Chengguang,
[FYI, it's a private test report for your RFC patch.]
[auto build test WARNING on miklos-vfs/overlayfs-next]
[also build test WARNING on linus/master v5.9-rc8 next-20201009]
[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/Chengguang-Xu/implement-containerized-syncfs-for-overlayfs/20201011-071405
base: https://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/vfs.git overlayfs-next
config: xtensa-allyesconfig (attached as .config)
compiler: xtensa-linux-gcc (GCC) 9.3.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/12d938a37e0a31d43b15e07aef1cd821bf11dc0e
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Chengguang-Xu/implement-containerized-syncfs-for-overlayfs/20201011-071405
git checkout 12d938a37e0a31d43b15e07aef1cd821bf11dc0e
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=xtensa
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
fs/overlayfs/super.c:400:6: warning: no previous prototype for 'ovl_evict_inode' [-Wmissing-prototypes]
400 | void ovl_evict_inode(struct inode *inode)
| ^~~~~~~~~~~~~~~
>> fs/overlayfs/super.c:410:5: warning: no previous prototype for 'ovl_write_inode' [-Wmissing-prototypes]
410 | int ovl_write_inode(struct inode *inode, struct writeback_control *wbc)
| ^~~~~~~~~~~~~~~
>> fs/overlayfs/super.c:432:5: warning: no previous prototype for 'ovl_drop_inode' [-Wmissing-prototypes]
432 | int ovl_drop_inode(struct inode *inode)
| ^~~~~~~~~~~~~~
vim +/ovl_write_inode +410 fs/overlayfs/super.c
399
> 400 void ovl_evict_inode(struct inode *inode)
401 {
402 struct inode *upper;
403
404 upper = ovl_inode_upper(inode);
405 if (upper)
406 ovl_unregister_mark_dirty_notify(OVL_I(inode));
407 clear_inode(inode);
408 }
409
> 410 int ovl_write_inode(struct inode *inode, struct writeback_control *wbc)
411 {
412 struct ovl_fs *ofs = inode->i_sb->s_fs_info;
413 struct super_block *upper_sb = ovl_upper_mnt(ofs)->mnt_sb;
414 struct inode *upper_inode = ovl_inode_upper(inode);
415 struct writeback_control upper_wbc = {
416 .nr_to_write = LONG_MAX,
417 .sync_mode = WB_SYNC_ALL,
418 .tagged_writepages = wbc->tagged_writepages,
419 .for_kupdate = wbc->for_kupdate,
420 .for_background = wbc->for_background,
421 .for_sync = 0,
422 .range_cyclic = wbc->range_cyclic,
423 .range_start = wbc->range_start,
424 .range_end = wbc->range_end,
425 };
426
427 if (!upper_sb->s_op->write_inode || !upper_inode)
428 return 0;
429 return upper_sb->s_op->write_inode(upper_inode, &upper_wbc);
430 }
431
> 432 int ovl_drop_inode(struct inode *inode)
433 {
434 struct inode *upper_inode;
435
436 upper_inode = ovl_inode_upper(inode);
437 if (!upper_inode)
438 return 1;
439 if (!(upper_inode->i_state & I_DIRTY_ALL))
440 return 1;
441
442 return generic_drop_inode(inode);
443 }
444
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 65077 bytes --]
next prev parent reply other threads:[~2020-10-11 3:10 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-10 14:23 [RFC PATCH 0/5] implement containerized syncfs for overlayfs Chengguang Xu
2020-10-10 14:23 ` [RFC PATCH 1/5] fs: introduce notifier list for vfs inode Chengguang Xu
2020-10-14 16:15 ` Jan Kara
2020-10-15 3:03 ` Chengguang Xu
2020-10-15 6:11 ` Amir Goldstein
2020-10-15 11:29 ` Chengguang Xu
2020-10-15 12:32 ` Amir Goldstein
2020-10-15 13:13 ` Chengguang Xu
2020-10-15 16:02 ` Amir Goldstein
2020-10-15 16:06 ` Amir Goldstein
2020-10-16 1:56 ` Chengguang Xu
2020-10-16 4:39 ` Amir Goldstein
2020-10-16 7:43 ` Chengguang Xu
2020-10-15 3:25 ` Al Viro
2020-10-15 3:42 ` Chengguang Xu
2020-10-15 4:57 ` Al Viro
2020-10-15 10:56 ` Chengguang Xu
2020-10-16 7:09 ` Chengguang Xu
2020-10-16 9:22 ` Jan Kara
2020-10-10 14:23 ` [RFC PATCH 2/5] fs: export symbol of writeback_single_inode() Chengguang Xu
2020-10-10 14:23 ` [RFC PATCH 3/5] ovl: setup overlayfs' private bdi Chengguang Xu
2020-10-10 14:23 ` [RFC PATCH 4/5] ovl: monitor marking dirty activity of underlying upper inode Chengguang Xu
2020-10-11 1:16 ` kernel test robot
2020-10-11 1:55 ` kernel test robot
2020-10-10 14:23 ` [RFC PATCH 5/5] ovl: impement containerized syncfs for overlayfs Chengguang Xu
2020-10-11 2:57 ` kernel test robot
2020-10-11 3:10 ` kernel test robot [this message]
2020-10-11 13:08 ` kernel test robot
2020-10-12 12:31 ` Dan Carpenter
2020-10-12 12:31 ` Dan Carpenter
-- strict thread matches above, loose matches on Subject: below --
2020-10-11 7:30 kernel 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=202010111114.J7fa41SK-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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 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.