| 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
| ||
|
Message-ID: <20111027203412.GB31669@fieldses.org> Date: Thu, 27 Oct 2011 16:34:12 -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 Tue, Oct 25, 2011 at 08:16:08PM -0700, Boaz Harrosh wrote: > On 10/25/2011 05:19 AM, J. Bruce Fields wrote: > > Boaz Harrosh (1): > > nfsd4: fix failure to end nfsd4 grace period > > > > Bruce hi. > > As I recall this failure I have experienced in early stages of the > 3.1-rcX series. I admit that I always run with Benny's pnfs tree, > but I do not think it is patches that Benny added from the 3.2 set > I think it is breakage introduced by the 3.1 merge window. > > Therefor I think that this patch must be sent to Stable@ otherwise > surly 3.1 Kernel users are to hit it. (You can escapee it) 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"?) --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/
Powered by blists - more mailing lists