linux-kernel - [2.6.23-rc3] NFSv4 client 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: <46C37958.7000401@garzik.org>
Date:	Wed, 15 Aug 2007 18:08:24 -0400
From:	Jeff Garzik <jeff@...zik.org>
To:	Trond Myklebust <trond.myklebust@....uio.no>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
CC:	Andrew Morton <akpm@...ux-foundation.org>
Subject: [2.6.23-rc3] NFSv4 client oops

While upgrading nfs-utils on my NFSv4 file server (F7 x86-64 
2.6.23-rc3), I got an oops on the NFSv4 client (FC6 x86-64 2.6.23-rc3), 
and communications stopped.

I rebooted the client, and everything was fine again.  Then, on the 
server, I removed an extra nfs-utils package left over from FC6, causing 
the nfs daemons to be restarted.  Another oops.

So it seems like whatever Fedora does during an nfs-utils upgrade __on 
the server__ is causing a remote oops __on the client__.

NFSv4 client kernel config also attached.

Never seen this problem before, but then again, never did a remote OS 
upgrade of the fileserver while running NFSv4 before.

	Jeff

View attachment "log.txt" of type "text/plain" (8449 bytes)

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