public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@zeniv.linux.org.uk>
To: Helge Deller <deller@gmx.de>
Cc: 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:33:30 +0100	[thread overview]
Message-ID: <YtdpegRORT8TMYD8@ZenIV> (raw)
In-Reply-To: <Ytdo7pNf5W4VMr2H@ZenIV>

On Wed, Jul 20, 2022 at 03:31:10AM +0100, Al Viro wrote:
> On Sat, Jul 16, 2022 at 07:27:30AM +0200, Helge Deller wrote:
> > [108564.845444] dentry = 000000031624e6c0
> 
> *blink*
> Is that really a plausible address of a kernel object on
> parisc?  Or is that "mangle pointers for security fetish^W
> purposes, lest somebody manages to get a useful information
> out of dmesg" in action?
> 
> > [108564.889437] spin_is_locked(&dentry->d_lock) = 0
> > [108564.945436] dname_external(dentry) = 0
> > [108564.993436] dentry->d_flags & DCACHE_NORCU = 0
> > [108565.045446] dentry->d_name.len = 3
> > [108565.089435] dentry->d_name.hash = 89116695
> > [108565.137435] dentry->d_lockref.count = -128
> > [108565.189434] dentry->d_flags = 32776
> 
> 0x8008, i.e. DCACHE_OP_DELETE | DCACHE_DENTRY_KILLED.  No
> DCACHE_PAR_LOOKUP in sight...
> 
> > [108569.801407] dentry = 000000016d7d0000
> > [108569.845407] spin_is_locked(&dentry->d_lock) = 0
> > [108569.901422] dname_external(dentry) = 0
> > [108569.949405] dentry->d_flags & DCACHE_NORCU = 0
> > [108570.001405] dentry->d_name.len = 10
> > [108570.045421] dentry->d_name.hash = e6582e53
> > [108570.093476] dentry->d_lockref.count = -128
> > [108570.145404] dentry->d_flags = 32776
> > [108570.189420] dentry->d_inode = 0000000000000000
> > [108570.241404] dentry->d_parent = 00000002332c2780
> > [108570.297403] dentry->d_u.d_rcu = 0x416be770
> 
> Ditto.  Pointers look really weird...

PS: I think I've caught what could be found on l-k; could you
please forward the rest (parisc list? private thread?) to
fsdevel or directly my way.

  reply	other threads:[~2022-07-20  2:33 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
2022-07-20  2:22         ` Al Viro
2022-07-20  2:31     ` Al Viro
2022-07-20  2:33       ` Al Viro [this message]
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=YtdpegRORT8TMYD8@ZenIV \
    --to=viro@zeniv.linux.org.uk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox