All of lore.kernel.org
 help / color / mirror / Atom feed
From: Boaz Harrosh <bharrosh@panasas.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	<linux-kernel@vger.kernel.org>, <linux-nfs@vger.kernel.org>
Subject: Re: nfsd (and lock) changes for 3.2
Date: Tue, 25 Oct 2011 20:16:08 -0700	[thread overview]
Message-ID: <4EA77B78.6080706@panasas.com> (raw)
In-Reply-To: <20111025121924.GA15662@fieldses.org>

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@kernel
I think you can just send the patch to <stable@kernel.org> and it
will be included.

(What other 3.1 bug fixes are missing)

Thanks
Boaz

  parent reply	other threads:[~2011-10-26  3:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-25 12:19 nfsd (and lock) changes for 3.2 J. Bruce Fields
2011-10-25 12:34 ` J. Bruce Fields
2011-10-26  4:41   ` Tom Tucker
2011-10-26  8:59     ` J. Bruce Fields
2011-10-26  3:16 ` Boaz Harrosh [this message]
2011-10-26  3:31   ` Boaz Harrosh
2011-10-27 20:34   ` J. Bruce Fields
2011-10-28  0:23     ` Boaz Harrosh
2011-10-28 14:42       ` J. Bruce Fields
2011-11-04 16:04         ` J. Bruce Fields
2011-11-04 16:50           ` Boaz Harrosh
2011-11-04 17:45             ` J. Bruce Fields
2011-11-07 16:21             ` Benny Halevy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4EA77B78.6080706@panasas.com \
    --to=bharrosh@panasas.com \
    --cc=bfields@fieldses.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.