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: <20080604141958.GA14148@redhat.com>
Date:	Wed, 4 Jun 2008 10:19:58 -0400
From:	Dave Jones <davej@...hat.com>
To:	Chuck Lever <chuck.lever@...cle.com>
Cc:	Trond Myklebust <Trond.Myklebust@...app.com>, chucklever@...il.com,
	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: NFS oops in 2.6.26rc4

On Fri, May 30, 2008 at 03:37:01PM -0400, Chuck Lever wrote:
 
 > > Something else of note which I hadn't seen before, usually things lock
 > > up just after that first oops. For some reason, today it survived
 > > a little longer, but things really went downhill fast.
 > > It survived a 'dmesg ; scp dmesg davej@...k', and then wedged solid.
 > > So as well as the oops, it seems we're corrupting memory too.
 > > For reference, this kernel has both SLUB_DEBUG and PAGEALLOC_DEBUG  
 > > enabled.
 > 
 > I haven't seen this kind of problem here with .26, but yes, it does  
 > look like something is clobbering memory during an NFS mount.
 > 
 > I introduced some NFS mount parsing changes in this commit range:
 > 
 >    2d767432..82d101d5
 > 
 > A quick bisect should show which, if any of these, is the guilty  
 > party.  If any of these are the problem, I suspect it's 3f8400d1.

I didn't get time to try this out yet (hopefully tomorrow).
In the meantime, we've just gotten word of another user seeing memory
corruption with nfs - https://bugzilla.redhat.com/show_bug.cgi?id=449958

	Dave

-- 
http://www.codemonkey.org.uk
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ