All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Ian Kent <raven@themaw.net>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Tejun Heo <tj@kernel.org>
Cc: kbuild-all@lists.01.org, Brice Goglin <brice.goglin@gmail.com>,
	Fox Chen <foxhlchen@gmail.com>,
	Rick Lindsley <ricklind@linux.vnet.ibm.com>,
	Al Viro <viro@ZenIV.linux.org.uk>,
	Miklos Szeredi <miklos@szeredi.hu>,
	David Howells <dhowells@redhat.com>,
	Eric Sandeen <sandeen@sandeen.net>,
	Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 1/4] kernfs: move revalidate to be near lookup
Date: Fri, 9 Apr 2021 11:39:31 +0800	[thread overview]
Message-ID: <202104091113.t5WZudSD-lkp@intel.com> (raw)
In-Reply-To: <161793089488.10062.4398328199044761298.stgit@mickey.themaw.net>

[-- Attachment #1: Type: text/plain, Size: 3396 bytes --]

Hi Ian,

I love your patch! Yet something to improve:

[auto build test ERROR on driver-core/driver-core-testing]
[also build test ERROR on v5.12-rc6 next-20210408]
[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/Ian-Kent/kernfs-proposed-locking-and-concurrency-improvement/20210409-091821
base:   https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git c2f3f755f5c717f3621b33ef06d974b9cec4a104
config: arm-defconfig (attached as .config)
compiler: arm-linux-gnueabi-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/a3608518cc551301c1c33dbf6976c360ea82a95c
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Ian-Kent/kernfs-proposed-locking-and-concurrency-improvement/20210409-091821
        git checkout a3608518cc551301c1c33dbf6976c360ea82a95c
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=arm 

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

Note: the linux-review/Ian-Kent/kernfs-proposed-locking-and-concurrency-improvement/20210409-091821 HEAD b2217b0abf0a4518541559173ff04138a6e4f083 builds fine.
      It only hurts bisectibility.

All errors (new ones prefixed by >>):

   fs/kernfs/dir.c: In function 'kernfs_dop_revalidate':
>> fs/kernfs/dir.c:1048:7: error: implicit declaration of function 'kernfs_active_read'; did you mean 'kernfs_active'? [-Werror=implicit-function-declaration]
    1048 |  if (!kernfs_active_read(kn))
         |       ^~~~~~~~~~~~~~~~~~
         |       kernfs_active
   cc1: some warnings being treated as errors


vim +1048 fs/kernfs/dir.c

  1032	
  1033	static int kernfs_dop_revalidate(struct dentry *dentry, unsigned int flags)
  1034	{
  1035		struct kernfs_node *kn;
  1036	
  1037		if (flags & LOOKUP_RCU)
  1038			return -ECHILD;
  1039	
  1040		/* Always perform fresh lookup for negatives */
  1041		if (d_really_is_negative(dentry))
  1042			goto out_bad_unlocked;
  1043	
  1044		kn = kernfs_dentry_node(dentry);
  1045		mutex_lock(&kernfs_mutex);
  1046	
  1047		/* The kernfs node has been deactivated */
> 1048		if (!kernfs_active_read(kn))
  1049			goto out_bad;
  1050	
  1051		/* The kernfs node has been moved? */
  1052		if (kernfs_dentry_node(dentry->d_parent) != kn->parent)
  1053			goto out_bad;
  1054	
  1055		/* The kernfs node has been renamed */
  1056		if (strcmp(dentry->d_name.name, kn->name) != 0)
  1057			goto out_bad;
  1058	
  1059		/* The kernfs node has been moved to a different namespace */
  1060		if (kn->parent && kernfs_ns_enabled(kn->parent) &&
  1061		    kernfs_info(dentry->d_sb)->ns != kn->ns)
  1062			goto out_bad;
  1063	
  1064		mutex_unlock(&kernfs_mutex);
  1065		return 1;
  1066	out_bad:
  1067		mutex_unlock(&kernfs_mutex);
  1068	out_bad_unlocked:
  1069		return 0;
  1070	}
  1071	

---
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: 54352 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH v3 1/4] kernfs: move revalidate to be near lookup
Date: Fri, 09 Apr 2021 11:39:31 +0800	[thread overview]
Message-ID: <202104091113.t5WZudSD-lkp@intel.com> (raw)
In-Reply-To: <161793089488.10062.4398328199044761298.stgit@mickey.themaw.net>

[-- Attachment #1: Type: text/plain, Size: 3484 bytes --]

Hi Ian,

I love your patch! Yet something to improve:

[auto build test ERROR on driver-core/driver-core-testing]
[also build test ERROR on v5.12-rc6 next-20210408]
[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/Ian-Kent/kernfs-proposed-locking-and-concurrency-improvement/20210409-091821
base:   https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git c2f3f755f5c717f3621b33ef06d974b9cec4a104
config: arm-defconfig (attached as .config)
compiler: arm-linux-gnueabi-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/a3608518cc551301c1c33dbf6976c360ea82a95c
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Ian-Kent/kernfs-proposed-locking-and-concurrency-improvement/20210409-091821
        git checkout a3608518cc551301c1c33dbf6976c360ea82a95c
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=arm 

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

Note: the linux-review/Ian-Kent/kernfs-proposed-locking-and-concurrency-improvement/20210409-091821 HEAD b2217b0abf0a4518541559173ff04138a6e4f083 builds fine.
      It only hurts bisectibility.

All errors (new ones prefixed by >>):

   fs/kernfs/dir.c: In function 'kernfs_dop_revalidate':
>> fs/kernfs/dir.c:1048:7: error: implicit declaration of function 'kernfs_active_read'; did you mean 'kernfs_active'? [-Werror=implicit-function-declaration]
    1048 |  if (!kernfs_active_read(kn))
         |       ^~~~~~~~~~~~~~~~~~
         |       kernfs_active
   cc1: some warnings being treated as errors


vim +1048 fs/kernfs/dir.c

  1032	
  1033	static int kernfs_dop_revalidate(struct dentry *dentry, unsigned int flags)
  1034	{
  1035		struct kernfs_node *kn;
  1036	
  1037		if (flags & LOOKUP_RCU)
  1038			return -ECHILD;
  1039	
  1040		/* Always perform fresh lookup for negatives */
  1041		if (d_really_is_negative(dentry))
  1042			goto out_bad_unlocked;
  1043	
  1044		kn = kernfs_dentry_node(dentry);
  1045		mutex_lock(&kernfs_mutex);
  1046	
  1047		/* The kernfs node has been deactivated */
> 1048		if (!kernfs_active_read(kn))
  1049			goto out_bad;
  1050	
  1051		/* The kernfs node has been moved? */
  1052		if (kernfs_dentry_node(dentry->d_parent) != kn->parent)
  1053			goto out_bad;
  1054	
  1055		/* The kernfs node has been renamed */
  1056		if (strcmp(dentry->d_name.name, kn->name) != 0)
  1057			goto out_bad;
  1058	
  1059		/* The kernfs node has been moved to a different namespace */
  1060		if (kn->parent && kernfs_ns_enabled(kn->parent) &&
  1061		    kernfs_info(dentry->d_sb)->ns != kn->ns)
  1062			goto out_bad;
  1063	
  1064		mutex_unlock(&kernfs_mutex);
  1065		return 1;
  1066	out_bad:
  1067		mutex_unlock(&kernfs_mutex);
  1068	out_bad_unlocked:
  1069		return 0;
  1070	}
  1071	

---
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: 54352 bytes --]

  reply	other threads:[~2021-04-09  3:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-09  1:14 [PATCH v3 0/4] kernfs: proposed locking and concurrency improvement Ian Kent
2021-04-09  1:14 ` [PATCH v3 1/4] kernfs: move revalidate to be near lookup Ian Kent
2021-04-09  3:39   ` kernel test robot [this message]
2021-04-09  3:39     ` kernel test robot
2021-04-09  1:15 ` [PATCH v3 2/4] kernfs: use VFS negative dentry caching Ian Kent
2021-04-09  1:35   ` Al Viro
2021-04-09  8:26     ` Ian Kent
2021-04-09  9:34       ` Ian Kent
2021-04-09  1:15 ` [PATCH v3 3/4] kernfs: switch kernfs to use an rwsem Ian Kent
2021-04-09  1:15 ` [PATCH v3 4/4] kernfs: use i_lock to protect concurrent inode updates Ian Kent
2021-04-19  7:56 ` [PATCH v3 0/4] kernfs: proposed locking and concurrency improvement Fox Chen
2021-04-19 12:25   ` Ian Kent

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=202104091113.t5WZudSD-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=brice.goglin@gmail.com \
    --cc=dhowells@redhat.com \
    --cc=foxhlchen@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=raven@themaw.net \
    --cc=ricklind@linux.vnet.ibm.com \
    --cc=sandeen@sandeen.net \
    --cc=tj@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.