All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luis Henriques <luis.henriques@canonical.com>
To: Trond Myklebust <Trond.Myklebust@netapp.com>
Cc: Jeff Layton <jlayton@redhat.com>,
	"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH 0/2] Fix regression on NFS in mainline kernel
Date: Thu, 19 Apr 2012 14:48:47 +0100	[thread overview]
Message-ID: <20120419134847.GC2916@zeus> (raw)
In-Reply-To: <20120419093025.GA2916@zeus>

On Thu, Apr 19, 2012 at 10:30:25AM +0100, Luis Henriques wrote:
> On Wed, Apr 18, 2012 at 01:36:52PM -0400, Trond Myklebust wrote:
> > The first patch addresses the Oops.
> > The second will hopefully address the looping.
> > 
> > Trond Myklebust (2):
> >   NFSv4: Ensure that the LOCK code sets exception->inode
> >   NFSv4: Ensure that we check lock exclusive/shared type against open
> >     modes
> > 
> >  fs/nfs/nfs4proc.c |   23 +++++++++++++++++++++--
> >  1 files changed, 21 insertions(+), 2 deletions(-)
> > 
> > -- 
> > 1.7.7.6
> > 
> Just to let you know we do have a few successful tests on these patches.
> You can check the details here:
> 
> http://bugs.launchpad.net/bugs/974664
> 
> Although I haven't tested the patches myself, fell free to add a Tested-by
> to these patches.

There's something else a forgot to mention, which is the fact that the bug
reports were for kernel 3.2.14.  So you may want to update the
"Cc: stable@vger.kernel.org" on commit 487790f27df9bb27d3400486bd021dd59edc7589
to include at least this version.

There are two another patches we have applied that are present in mainline
but haven't made its way into stable:
 - 14977489ffdb80d4caf5a184ba41b23b02fbacd9
 - 96dcadc2fdd111dca90d559f189a30c65394451a

Cheers,
--
Luis

  reply	other threads:[~2012-04-19 13:49 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-18 11:26 Regretion on NFS in mainline kernel Luis Henriques
2012-04-18 13:28 ` Jeff Layton
2012-04-18 13:57   ` Luis Henriques
2012-04-18 14:04     ` Myklebust, Trond
2012-04-18 14:13       ` Luis Henriques
2012-04-18 14:15         ` Jeff Layton
2012-04-18 14:41           ` Myklebust, Trond
2012-04-18 14:51             ` Jeff Layton
2012-04-18 17:35               ` Luis Henriques
2012-04-18 17:36               ` [PATCH 0/2] Fix regression " Trond Myklebust
2012-04-18 17:42                 ` Jeff Layton
2012-04-18 17:50                 ` Luis Henriques
2012-04-19  9:30                 ` Luis Henriques
2012-04-19 13:48                   ` Luis Henriques [this message]
2012-04-19 17:29                     ` Myklebust, Trond
2012-04-19 20:46                       ` Luis Henriques
2013-01-04 10:05                         ` Mario Bachmann
2013-01-04 14:15                           ` Myklebust, Trond
2013-01-06 10:48                             ` Mario Bachmann
2012-04-18 17:36               ` [PATCH 1/2] NFSv4: Ensure that the LOCK code sets exception->inode Trond Myklebust
2012-04-18 17:36               ` [PATCH 2/2] NFSv4: Ensure that we check lock exclusive/shared type against open modes Trond Myklebust

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=20120419134847.GC2916@zeus \
    --to=luis.henriques@canonical.com \
    --cc=Trond.Myklebust@netapp.com \
    --cc=jlayton@redhat.com \
    --cc=linux-nfs@vger.kernel.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.