linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Boaz Harrosh <bharrosh@panasas.com>
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: Fri, 28 Oct 2011 10:42:52 -0400	[thread overview]
Message-ID: <20111028144252.GB5798@fieldses.org> (raw)
In-Reply-To: <4EA9F5E8.6060900@panasas.com>

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@kernel.org?  Cc: me and I'll
ack them.

--b.

  reply	other threads:[~2011-10-28 14:42 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
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 [this message]
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=20111028144252.GB5798@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=bharrosh@panasas.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).