linux-kernel - Re: nfsd (and lock) changes for 3.2

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

Date:	Fri, 28 Oct 2011 10:42:52 -0400
From:	"J. Bruce Fields" <bfields@...ldses.org>
To:	Boaz Harrosh <bharrosh@...asas.com>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, linux-nfs@...r.kernel.org
Subject: Re: nfsd (and lock) changes for 3.2

On Thu, Oct 27, 2011 at 05:23:04PM -0700, Boaz Harrosh wrote:
> On 10/27/2011 01:34 PM, J. Bruce Fields wrote:
> > We need to test it, but I think you're probably correct,
> > 6577aac01f00636c16cd583c30bd4dedf18475d5 "nfsd4: fix failure to end
> > nfsd4 grace period" should have been tagged for stable.  Does that also
> > require any previous patches? (E.g.
> > 48483bf23a568f3ef4cc7ad2c8f1a082f10ad0e7 "nfsd4: simplify recovery dir
> > setting"?)
> > 
> 
> right, and all for that dmesg print. But yes! 
> 
> Well the 3.1 Kernel without them gets stuck. I guess you need to experiment
> with what would be the minimal patchset needed for 3.1 .
> 
> Tell me if you need help testing that the damage has gone. But basically I have
> a script (4 years old) that does: 
> 	server: service nfs stop/start 
> 	client: mount
> back to back, The client gets stuck forever.

You and I are pretty sure those patches are needed, and fix the problem.
But it would probably be a good idea, to make sure.

Would you mind passing both along to stable@...nel.org?  Cc: me and I'll
ack them.

--b.
--
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/