From: Richard Ems <richard.ems@cape-horn-eng.com>
To: Trond Myklebust <Trond.Myklebust@netapp.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH] NFS: Fix Oopses in nfs_lookup_revalidate and nfs4_lookup_revalidate
Date: Tue, 21 Aug 2012 12:23:43 +0200 [thread overview]
Message-ID: <503361AF.8030707@cape-horn-eng.com> (raw)
In-Reply-To: <1345063762-32530-1-git-send-email-Trond.Myklebust@netapp.com>
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
next prev parent reply other threads:[~2012-08-21 10:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-15 20:49 [PATCH] NFS: Fix Oopses in nfs_lookup_revalidate and nfs4_lookup_revalidate Trond Myklebust
2012-08-15 20:50 ` Myklebust, Trond
2012-08-21 10:23 ` Richard Ems [this message]
2012-09-19 11:18 ` Fwd: " Richard Ems
2012-09-19 12:52 ` Greg KH
2012-09-19 13:16 ` Myklebust, Trond
2012-09-28 0:21 ` gregkh
-- strict thread matches above, loose matches on Subject: below --
2012-08-22 20:08 Trond Myklebust
2012-08-27 20:09 ` Greg KH
2012-08-27 20:16 ` Myklebust, Trond
2012-08-27 20:16 ` Myklebust, Trond
2012-08-27 20:23 ` Greg KH
2012-08-28 18:56 ` Jeff Layton
2012-08-27 21:34 ` Ben Hutchings
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=503361AF.8030707@cape-horn-eng.com \
--to=richard.ems@cape-horn-eng.com \
--cc=Trond.Myklebust@netapp.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.