linux-kernel - Re: fs: use after free in /proc/pid/mountinfo

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]

Message-ID: <alpine.DEB.2.02.1407151558450.32274@chino.kir.corp.google.com>
Date:	Tue, 15 Jul 2014 16:01:34 -0700 (PDT)
From:	David Rientjes <rientjes@...gle.com>
To:	Sasha Levin <sasha.levin@...cle.com>
cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Heiko Carstens <heiko.carstens@...ibm.com>,
	linux-fsdevel <linux-fsdevel@...r.kernel.org>,
	Al Viro <viro@...iv.linux.org.uk>, Jan Kara <jack@...e.cz>,
	Dave Jones <davej@...hat.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: fs: use after free in /proc/pid/mountinfo

On Tue, 15 Jul 2014, Sasha Levin wrote:

> I've been running mainline for a while, and while I can reproduce a different
> bug for Hugh, I can't reproduce this one at all. Not sure how to call it now,
> maybe memory corruption from somewhere else (I did find an unrelated memory
> corruption couple days ago)?
> 

I have a very large /proc/pid/mountinfo on one of my busy systems with VM 
and slub debugging enabled and have not been able to reproduce the issue 
while reading it in a loop for 24 hours.  I would call the patch good on 
that basis, but it's very strange you'd report this problem a day after 
the patch was merged and could not reproduce it once it was reverted.  
(Unless the patch was misapplied locally and reapplying it now worked, but 
I doubt you originally merged -mm patches into a local tree yourself.)
--
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/