From: Al Viro <viro@zeniv.linux.org.uk>
To: Helge Deller <deller@gmx.de>
Cc: John David Anglin <dave.anglin@bell.net>,
Hillf Danton <hdanton@sina.com>,
linux-kernel@vger.kernel.org, linux-parisc@vger.kernel.org
Subject: Re: WARNING: CPU: 1 PID: 14735 at fs/dcache.c:365 dentry_free+0x100/0x128
Date: Wed, 20 Jul 2022 03:00:23 +0100 [thread overview]
Message-ID: <YtdhtyiEOGFhYdfP@ZenIV> (raw)
In-Reply-To: <76e47f90-bcc2-caab-50c5-6bff7fdc5c1d@gmx.de>
On Tue, Jul 19, 2022 at 11:25:07PM +0200, Helge Deller wrote:
> On 7/19/22 22:59, John David Anglin wrote:
> > Hi Helge,
> >
> > I hit this warning with the patch below building ghc on mx3210:
>
> As I wrote, I didn't faced it yet on my buildd server, but that could
> just have been luck...
> Hillf, should we try if this second hunk triggers?
>
> --- a/fs/dcache.c
> +++ b/fs/dcache.c
> @@ -616,6 +618,7 @@ static void __dentry_kill(struct dentry
> dentry->d_flags |= DCACHE_MAY_FREE;
> can_free = false;
> }
> + BUG_ON(!hlist_unhashed(&dentry->d_u.d_alias));
> spin_unlock(&dentry->d_lock);
> if (likely(can_free))
> dentry_free(dentry);
Would you gentlemen mind Cc'ing the entire thing to fsdevel? Or at
least forwarding it my way...
next prev parent reply other threads:[~2022-07-20 2:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220709090756.2384-1-hdanton@sina.com>
2022-07-15 8:18 ` WARNING: CPU: 1 PID: 14735 at fs/dcache.c:365 dentry_free+0x100/0x128 Helge Deller
[not found] ` <20220715133300.1297-1-hdanton@sina.com>
2022-07-16 5:27 ` Helge Deller
2022-07-17 9:42 ` Helge Deller
[not found] ` <20220717113634.1552-1-hdanton@sina.com>
2022-07-19 16:32 ` Helge Deller
2022-07-19 20:59 ` John David Anglin
2022-07-19 21:25 ` Helge Deller
2022-07-20 2:00 ` Al Viro [this message]
2022-07-20 2:22 ` Al Viro
2022-07-20 2:31 ` Al Viro
2022-07-20 2:33 ` Al Viro
2022-07-20 3:29 ` Al Viro
2022-07-20 6:53 ` Helge Deller
2022-07-20 7:07 ` Al Viro
2022-07-20 9:21 ` Helge Deller
[not found] ` <20220720110032.1787-1-hdanton@sina.com>
2022-07-20 17:06 ` Al Viro
2022-07-20 23:15 ` Sam James
2022-07-21 3:54 ` Helge Deller
2022-07-30 20:21 ` Helge Deller
2022-07-09 5:33 Helge Deller
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=YtdhtyiEOGFhYdfP@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=dave.anglin@bell.net \
--cc=deller@gmx.de \
--cc=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.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.