From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bruce Fields Subject: Re: [git pull] fixes for 3.12-final Date: Wed, 18 Dec 2013 14:40:34 -0500 Message-ID: <20131218194034.GA22259@fieldses.org> References: <20131103015803.GK13318@ZenIV.linux.org.uk> <20131103195452.GL13318@ZenIV.linux.org.uk> <20131104005300.GM13318@ZenIV.linux.org.uk> <20131106151003.GA21425@ZenIV.linux.org.uk> <20131113144353.GE28033@fieldses.org> <20131113151655.GG28033@fieldses.org> <20131118163243.GA30944@kroah.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Al Viro , Linus Torvalds , Linux Kernel Mailing List , linux-fsdevel , stable@vger.kernel.org To: Greg KH Return-path: Content-Disposition: inline In-Reply-To: <20131118163243.GA30944@kroah.com> Sender: stable-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org 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 --b.