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

Date:	Tue, 25 Oct 2011 20:16:08 -0700
From:	Boaz Harrosh <bharrosh@...asas.com>
To:	"J. Bruce Fields" <bfields@...ldses.org>
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 10/25/2011 05:19 AM, J. Bruce Fields wrote:
> Changes for nfsd (and also a few file-locking changes) are available in
> the git repository at:
> 
> 	git://linux-nfs.org/~bfields/linux.git for-3.2
> 
> This is the same tree I've always used--I assume you believe it's mine
> without a need for signing anything.  Feel free to tell me otherwise.
> 

<Snip>

> 
> 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)

Though it has been pulled to Linus tree, without the CC: stable@...nel
I think you can just send the patch to <stable@...nel.org> and it
will be included.

(What other 3.1 bug fixes are missing)

Thanks
Boaz
--
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/