linux-kernel - 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: <480C6064.10801@gmail.com>
Date:	Mon, 21 Apr 2008 11:37:40 +0200
From:	Jiri Slaby <jirislaby@...il.com>
To:	Al Viro <viro@...IV.linux.org.uk>
CC:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org
Subject: fault in __d_lookup [Was: 2.6.25-mm1]

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)?
--
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/