From: Al Viro <viro@zeniv.linux.org.uk>
To: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-fsdevel@vger.kernel.org
Subject: Re: [viro-vfs:carved-up-__dentry_kill 22/28] fs/dcache.c:1101:33: error: 'dentry' undeclared
Date: Wed, 6 Dec 2023 01:01:34 +0000 [thread overview]
Message-ID: <20231206010134.GK1674809@ZenIV> (raw)
In-Reply-To: <202312060802.HxDqIoDc-lkp@intel.com>
On Wed, Dec 06, 2023 at 08:29:37AM +0800, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git carved-up-__dentry_kill
> head: 20f7d1936e8a2859fee51273c8ffadcca4304968
> commit: c73bce0494d44e0d26ec351106558e4408cf1cd9 [22/28] step 3: have __dentry_kill() return the parent
> config: x86_64-rhel-8.3 (https://download.01.org/0day-ci/archive/20231206/202312060802.HxDqIoDc-lkp@intel.com/config)
> compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231206/202312060802.HxDqIoDc-lkp@intel.com/reproduce)
>
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202312060802.HxDqIoDc-lkp@intel.com/
>
> Note: the viro-vfs/carved-up-__dentry_kill HEAD 20f7d1936e8a2859fee51273c8ffadcca4304968 builds fine.
> It only hurts bisectability.
Argh... carve-up fuckups... delta to fix that one up follows,
the breakage actually disappears on the next step. Sorry about that...
Updated branch force-pushed
diff --git a/fs/dcache.c b/fs/dcache.c
index b35d120193e0..fc8347b8ac98 100644
--- a/fs/dcache.c
+++ b/fs/dcache.c
@@ -1098,10 +1098,10 @@ EXPORT_SYMBOL(d_prune_aliases);
static inline void shrink_kill(struct dentry *victim, struct list_head *list)
{
- struct dentry *parent = dentry->d_parent;
- if (parent != victim && if (!--parent->d_lockref.count)
+ struct dentry *parent = victim->d_parent;
+ if (parent != victim && !--parent->d_lockref.count)
to_shrink_list(parent, list);
- parent = __dentry_kill(dentry);
+ parent = __dentry_kill(victim);
if (parent)
spin_unlock(&parent->d_lock);
}
prev parent reply other threads:[~2023-12-06 1:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-06 0:29 [viro-vfs:carved-up-__dentry_kill 22/28] fs/dcache.c:1101:33: error: 'dentry' undeclared kernel test robot
2023-12-06 1:01 ` Al Viro [this message]
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=20231206010134.GK1674809@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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;
as well as URLs for NNTP newsgroup(s).