linux-kernel - Re: [bisect] NFS regression breaks X

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: <20070509155228.d1b9d644.akpm@linux-foundation.org>
Date:	Wed, 9 May 2007 15:52:28 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Trond Myklebust <Trond.Myklebust@...app.com>
Cc:	Jeff Garzik <jeff@...zik.org>,
	Chuck Lever <chuck.lever@...cle.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	NeilBrown <neilb@...e.de>, Adrian Bunk <bunk@...sta.de>
Subject: Re: [bisect] NFS regression breaks X

On Wed, 09 May 2007 18:03:26 -0400
Trond Myklebust <Trond.Myklebust@...app.com> wrote:

> On Wed, 2007-05-09 at 17:30 -0400, Jeff Garzik wrote:
> > Original bug report, with hardware and software info:
> > http://lkml.org/lkml/2007/5/8/667
> > 
> > I love bisect :)  bisect has identified the following commit as the one 
> > that causes my GNOME login to die, within 10 seconds of logging in:
> > 
> > 	commit 2bea90d43a050bbc4021d44e59beb34f384438db
> > 	Author: Chuck Lever <chuck.lever@...cle.com>
> > 	Date:   Thu Mar 29 16:47:53 2007 -0400
> > 
> > 	SUNRPC: RPC buffer size estimates are too large
> > 
> > 100% reproducible, verified regression.  My home directory is an NFSv4 
> > mount, and the problem appears on my client workstation, so this makes 
> > some sense:
> > > sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
> > > pretzel:/ on /g type nfs4 (rw,noatime,proto=tcp,addr=10.10.10.1)
> 
> Known issue.

It's a bit rough that Jeff spent a large amount of time hunting down an
already-known bug.  That's normally my job :(

This five-week-old diff only ever appeared in 2.6.21-mm1, which was
released four days ago.  It was then whizzed into mainline.  We thus lost
five weeks public testing which would probably have saved Jeff his pain.

What went wrong?
-
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/