linux-kernel - Re: WARNING: CPU: 1 PID: 14735 at fs/dcache.c:365 dentry

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 20 Jul 2022 08:07:07 +0100
From:   Al Viro <viro@...iv.linux.org.uk>
To:     Helge Deller <deller@....de>
Cc:     Hillf Danton <hdanton@...a.com>, linux-kernel@...r.kernel.org,
        linux-parisc@...r.kernel.org
Subject: Re: WARNING: CPU: 1 PID: 14735 at fs/dcache.c:365
 dentry_free+0x100/0x128

On Wed, Jul 20, 2022 at 08:53:53AM +0200, Helge Deller wrote:
> On 7/20/22 05:29, Al Viro wrote:
> > On Sat, Jul 16, 2022 at 07:27:30AM +0200, Helge Deller wrote:
> >> On 7/15/22 15:33, Hillf Danton wrote:
> >
> >> [108565.341434] dentry->d_u.d_rcu = 0x416be770
> >
> > Incidentally, does that match the address of __d_free() on your build,
> > or is it something different?
> 
> I don't think it's __d_free().
> The source is:
> 	pr_err("dentry->d_u.d_rcu = %pS\n", dentry->d_u.d_rcu.func);
> so the "%pS" would probably have resolved the pointer to string "__d_free" (or something else).

????

That should've taken a word from desc->addr and printed it.
If it had managed to get to a string (you'd needed to have
CONFIG_KALLSYMS enabled), it would've printed it as a string,
not as hex address.  Seriously, check System.map for that
kernel...