linux-kernel - Re: [git pull] fixes for 3.12-final

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 18 Nov 2013 08:32:43 -0800
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Bruce Fields <bfields@...ldses.org>
Cc:	Al Viro <viro@...IV.linux.org.uk>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linux-fsdevel <linux-fsdevel@...r.kernel.org>,
	stable@...r.kernel.org
Subject: Re: [git pull] fixes for 3.12-final

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@...r.kernel.org.

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/