From: Bruce Fields <bfields@fieldses.org>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: 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, 13 Nov 2013 10:16:55 -0500 [thread overview]
Message-ID: <20131113151655.GG28033@fieldses.org> (raw)
In-Reply-To: <20131113144353.GE28033@fieldses.org>
(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"
--b.
next prev parent reply other threads:[~2013-11-13 15:17 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 [this message]
2013-11-18 16:32 ` Greg KH
2013-12-18 19:40 ` Bruce Fields
2013-12-18 20:12 ` Greg KH
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=20131113151655.GG28033@fieldses.org \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox