mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Richard Ems <richard.ems@cape-horn-eng.com>
To: "Myklebust, Trond" <Trond.Myklebust@netapp.com>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
	linux-kernel@vger.kernel.org, gregkh@linuxfoundation.org
Subject: Fwd: Re: [PATCH] NFS: Fix Oopses in nfs_lookup_revalidate and nfs4_lookup_revalidate
Date: Wed, 19 Sep 2012 13:18:08 +0200	[thread overview]
Message-ID: <5059A9F0.2070409@cape-horn-eng.com> (raw)
In-Reply-To: <503361AF.8030707@cape-horn-eng.com>

Hi all,

I still don't see this patch in the 3.5.x series.
Will it make it into 3.5.5?

Thanks,
Richard


-------- Original Message --------
Subject: Re: [PATCH] NFS: Fix Oopses in nfs_lookup_revalidate and
nfs4_lookup_revalidate
Date: Tue, 21 Aug 2012 12:23:43 +0200
From: Richard Ems <richard.ems@cape-horn-eng.com>
To: Trond Myklebust <Trond.Myklebust@netapp.com>
CC: linux-nfs@vger.kernel.org

On 08/15/2012 10:49 PM, Trond Myklebust wrote:
> This Oops affects 3.5 kernels and older, and is due to lookup_one_len()
> calling down to the dentry revalidation code with a NULL pointer
> to struct nameidata.
> 
> It is fixed upstream by commit 0b728e1911c (stop passing nameidata *
> to ->d_revalidate())
> 
> Reported-by: Richard Ems <richard.ems@cape-horn-eng.com>
> Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>


Hi Trond,

I don't see this patch going into 3.5.3 at
http://www.kernel.org/pub/linux/kernel/v3.0/stable-review/patch-3.5.3-rc1.gz
.
Shouldn't it be included in 3.5.3 ?

Thanks,
Richard


-- 
Richard Ems       mail: Richard.Ems@Cape-Horn-Eng.com

Cape Horn Engineering S.L.
C/ Dr. J.J. Dómine 1, 5º piso
46011 Valencia
Tel : +34 96 3242923 / Fax 924
http://www.cape-horn-eng.com



       reply	other threads:[~2012-09-19 11:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <503361AF.8030707@cape-horn-eng.com>
2012-09-19 11:18 ` Richard Ems [this message]
2012-09-19 12:52   ` Greg KH
2012-09-19 13:16   ` Myklebust, Trond
2012-09-28  0:21     ` gregkh

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=5059A9F0.2070409@cape-horn-eng.com \
    --to=richard.ems@cape-horn-eng.com \
    --cc=Trond.Myklebust@netapp.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®