> -----Original Message----- > From: [email protected] [mailto:linux-nfs- > [email protected]] On Behalf Of Richard Ems > Sent: Wednesday, September 19, 2012 7:18 AM > To: Myklebust, Trond > Cc: [email protected]; [email protected]; > [email protected] > Subject: Fwd: Re: [PATCH] NFS: Fix Oopses in nfs_lookup_revalidate and > nfs4_lookup_revalidate > > 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 Hi Greg,
I believe you said that you would take this patch. Do you want me to resend? Cheers, Trond > -------- 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 <[email protected]> > To: Trond Myklebust <[email protected]> > CC: [email protected] > > 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 <[email protected]> > > Signed-off-by: Trond Myklebust <[email protected]> > > > 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: [email protected] > > 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 > > > -- > To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the > body of a message to [email protected] More majordomo info at > http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
