linux-kernel - 2.6.31-rc3 nfsv4 client regression (oops)

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-next>] [day] [month] [year] [list]

Message-ID: <4A5C3858.6070303@garzik.org>
Date:	Tue, 14 Jul 2009 03:48:40 -0400
From:	Jeff Garzik <jeff@...zik.org>
To:	LKML <linux-kernel@...r.kernel.org>
CC:	Trond Myklebust <Trond.Myklebust@...app.com>,
	Linux NFS ML <linux-nfs@...r.kernel.org>,
	"Rafael J. Wysocki" <rjw@...k.pl>
Subject: 2.6.31-rc3 nfsv4 client regression (oops)


The NFSv4 client just oops'd on me...

NFSv4 client: 2.6.31-rc3, Fedora 10, x86-64
		    2.6.30 works, I think 2.6.31-rc1 worked too

NFSv4 server: 2.6.29.4-167.fc11.x86_64 (Fedora 11 kernel), F11, x86-64

Oops output captured at kerneloops.org: 
http://www.kerneloops.org/raw.php?rawid=537858&msgid=

Kernel config for 2.6.31-rc3, the problematic kernel, attached.


> RIP: 0010:[<ffffffffa02db5b0>]  [<ffffffffa02db5b0>] nfs4_free_lock_state+0x20/0x80 [nfs]
> [...]
> Call Trace:
>  [<ffffffffa02db7dd>] nfs4_set_lock_state+0x1cd/0x220 [nfs]
>  [<ffffffffa02cc9db>] nfs4_proc_lock+0x2cb/0x4e0 [nfs]
>  [<ffffffff810b40dc>] ? __alloc_pages_nodemask+0x10c/0x600
>  [<ffffffffa02b6079>] do_setlk+0xb9/0xd0 [nfs]
>  [<ffffffffa02b6220>] nfs_lock+0xd0/0x1d0 [nfs]
>  [<ffffffff8111e883>] vfs_lock_file+0x23/0x50
>  [<ffffffff8111eaa3>] fcntl_setlk+0x133/0x2f0
>  [<ffffffff81192571>] ? __up_read+0x91/0xb0
>  [<ffffffff810f0fea>] sys_fcntl+0xca/0x420
>  [<ffffffff8100b4fb>] system_call_fastpath+0x16/0x1b




View attachment "config.txt" of type "text/plain" (61676 bytes)