linux-kernel - Re: fault in __d_lookup [Was: 2.6.25-mm1]

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]

Message-ID: <20080421094515.GR27459@ZenIV.linux.org.uk>
Date:	Mon, 21 Apr 2008 10:45:15 +0100
From:	Al Viro <viro@...IV.linux.org.uk>
To:	Jiri Slaby <jirislaby@...il.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org
Subject: Re: fault in __d_lookup [Was: 2.6.25-mm1]

On Mon, Apr 21, 2008 at 11:37:40AM +0200, Jiri Slaby wrote:
> On 04/21/2008 11:06 AM, Al Viro wrote:
> >On Mon, Apr 21, 2008 at 10:31:40AM +0200, Jiri Slaby wrote:
> >
> >        hlist_for_each_entry_rcu(dentry, node, head, d_hash) {
> >                struct qstr *qstr;
> >
> >                if (dentry->d_name.hash != hash)
> >                        continue;
> >
> >walking into node == (struct hlist_node *)0x00f0000000000000...
> 
> Yup, true, In the last oops I stuck on memcmp few lines below.
> 
> BTW. it's 100% reproducible after it happens once, but fixable by reboot. 
> Any tests I should run (memtest, some printks sticked anywhere)?

Well, if list has such turd in it, you'll certainly hit it every time
you walk that list, so 100% reproducible is not surprising.

How well is it reproducible from fresh boot?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/