From: Greg KH <gregkh@linuxfoundation.org>
To: Bruce Fields <bfields@fieldses.org>
Cc: Al Viro <viro@ZenIV.linux.org.uk>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
stable@vger.kernel.org
Subject: Re: [git pull] fixes for 3.12-final
Date: Wed, 18 Dec 2013 12:12:49 -0800 [thread overview]
Message-ID: <20131218201249.GC16267@kroah.com> (raw)
In-Reply-To: <20131218194034.GA22259@fieldses.org>
On Wed, Dec 18, 2013 at 02:40:34PM -0500, Bruce Fields wrote:
> On Mon, Nov 18, 2013 at 08:32:43AM -0800, Greg KH wrote:
> > On Wed, Nov 13, 2013 at 10:16:55AM -0500, Bruce Fields wrote:
> > > (Argh, sorry, with the right stable address cc'd this time I hope.)
> > >
> > > On Wed, Nov 06, 2013 at 03:10:04PM +0000, Al Viro wrote:
> > > > FWIW, not taking ->i_lock there definitely looks like a good thing. As for
> > > > 64bit ->i_ino itself... Looks like the main problem is the shitload of
> > > > printks - the actual uses of ->i_ino are fine, but these suckers create
> > > > a lot of noise. So for now I'm going with Bruce's variant; 64bit i_ino
> > > > doesn't look too bad (even on i386, actually), but it'll have to wait
> > > > until 3.14. Too noisy and late in this cycle...
> > >
> > > I believe we also want that in stable?
> > >
> > > 950ee9566a5b6cc45d15f5fe044bab4f1e8b62cb "exportfs: fix 32-bit nfsd
> > > handling of 64-bit inode numbers"
> >
> > It breaks the build in 3.12 and others so if it is needed, please
> > provide a backport that works properly to stable@vger.kernel.org.
>
> Oops--there was a prerequisite patch that I forgot. So we actually want
>
> git cherry-pick b7a6ec52dd4eced4a9bcda9ca85b3c8af84d3c90
> git cherry-pick 950ee9566a5b6cc45d15f5fe044bab4f1e8b62cb
Thanks, I'll go take them now.
greg k-h
next prev parent reply other threads:[~2013-12-18 20:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-03 1:58 [git pull] fixes for 3.12-final Al Viro
2013-11-03 18:25 ` Linus Torvalds
2013-11-03 19:54 ` Al Viro
2013-11-03 23:39 ` Linus Torvalds
2013-11-04 0:53 ` Al Viro
2013-11-06 15:10 ` Al Viro
2013-11-13 14:43 ` Bruce Fields
2013-11-13 15:16 ` Bruce Fields
2013-11-18 16:32 ` Greg KH
2013-12-18 19:40 ` Bruce Fields
2013-12-18 20:12 ` Greg KH [this message]
2013-11-04 22:30 ` Bruce Fields
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=20131218201249.GC16267@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=bfields@fieldses.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@ZenIV.linux.org.uk \
/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.