linux-kernel - 2.6.19 nfsd 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>] [day] [month] [year] [list]

Message-ID: <45795A10.6080901@garzik.org>
Date:	Fri, 08 Dec 2006 07:26:56 -0500
From:	Jeff Garzik <jeff@...zik.org>
To:	Linux Kernel <linux-kernel@...r.kernel.org>
CC:	Andrew Morton <akpm@...l.org>, Neil Brown <neilb@...e.de>
Subject: 2.6.19 nfsd oops

After running fine for 8 days, my NFS fileserver suddenly oops'd in the 
NFS (see first attachment).

Data points:
* system: Intel x86-64, Fedora Core 5
* kernel: unpatched 2.6.19 release kernel
* from the syslog, it appears that the event coincided with a Fedora 
Core 5 nfs-utils package upgrade
* the oops appears to be workqueue-related, but that might just be the 
callsite
* I recently started (again) switching clients from NFSv3 to NFSv4. 
This may or may not be related to the oops.

I've attached the dmesg and .config from 2.6.19-gbff19b1d, which is the 
kernel it is currently running.  This is just to give a better picture 
of the machine.  As I noted above, the oops was from kernel 2.6.19 not 
2.6.19-gbff19b1d.

	Jeff

View attachment "messages" of type "text/plain" (4256 bytes)

Download attachment "dmesg.txt.gz" of type "application/x-gzip" (6573 bytes)

Download attachment "config.txt.gz" of type "application/x-gzip" (8521 bytes)