From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [RFC PATCH 4/5] ovl: monitor marking dirty activity of underlying upper inode
Date: Sun, 11 Oct 2020 09:55:15 +0800 [thread overview]
Message-ID: <202010110946.RUQ2CeZi-lkp@intel.com> (raw)
In-Reply-To: <20201010142355.741645-5-cgxu519@mykernel.net>
[-- Attachment #1: Type: text/plain, Size: 4077 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: arm-randconfig-r034-20201011 (attached as .config)
compiler: clang version 12.0.0 (https://github.com/llvm/llvm-project a8682554c6662ce01853d0069afb6c5b4ef8ab55)
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
# install arm cross compiling tool for clang build
# apt-get install binutils-arm-linux-gnueabi
# https://github.com/0day-ci/linux/commit/6a0553975f03bb63033f5c246273010a38a66ccf
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 6a0553975f03bb63033f5c246273010a38a66ccf
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=arm
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:393:6: warning: no previous prototype for function 'ovl_evict_inode' [-Wmissing-prototypes]
void ovl_evict_inode(struct inode *inode)
^
fs/overlayfs/super.c:393:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
void ovl_evict_inode(struct inode *inode)
^
static
1 warning generated.
--
fs/overlayfs/util.c:959:7: warning: unused variable 'flags' [-Wunused-variable]
int *flags = (int *)param;
^
fs/overlayfs/util.c:958:20: warning: unused variable 'oi' [-Wunused-variable]
struct ovl_inode *oi = container_of(nb, struct ovl_inode, mark_dirty_nb);
^
>> fs/overlayfs/util.c:955:5: warning: no previous prototype for function 'ovl_inode_dirty_notify' [-Wmissing-prototypes]
int ovl_inode_dirty_notify(struct notifier_block *nb,
^
fs/overlayfs/util.c:955:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
int ovl_inode_dirty_notify(struct notifier_block *nb,
^
static
3 warnings generated.
--
fs/overlayfs/util.c:958:20: warning: unused variable 'oi' [-Wunused-variable]
struct ovl_inode *oi = container_of(nb, struct ovl_inode, mark_dirty_nb);
^
fs/overlayfs/util.c:959:7: warning: unused variable 'flags' [-Wunused-variable]
int *flags = (int *)param;
^
>> fs/overlayfs/util.c:955:5: warning: no previous prototype for function 'ovl_inode_dirty_notify' [-Wmissing-prototypes]
int ovl_inode_dirty_notify(struct notifier_block *nb,
^
fs/overlayfs/util.c:955:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
int ovl_inode_dirty_notify(struct notifier_block *nb,
^
static
3 warnings generated.
vim +/ovl_evict_inode +393 fs/overlayfs/super.c
392
> 393 void ovl_evict_inode(struct inode *inode)
394 {
395 struct inode *upper;
396
397 upper = ovl_inode_upper(inode);
398 if (upper)
399 ovl_unregister_mark_dirty_notify(OVL_I(inode));
400 clear_inode(inode);
401 }
402
---
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: 33109 bytes --]
next prev parent reply other threads:[~2020-10-11 1:55 UTC|newest]
Thread overview: 30+ 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 [this message]
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
2020-10-11 13:08 ` kernel test robot
2020-10-12 12:31 ` Dan Carpenter
2020-10-12 12:31 ` Dan Carpenter
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=202010110946.RUQ2CeZi-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.