linux-kernel - Re: fs/stat: Reduce memory requirements for stat

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.1406241642280.22030@chino.kir.corp.google.com>
Date:	Tue, 24 Jun 2014 16:44:00 -0700 (PDT)
From:	David Rientjes <rientjes@...gle.com>
To:	Stefan Bader <stefan.bader@...onical.com>
cc:	Heiko Carstens <heiko.carstens@...ibm.com>,
	linux-kernel@...r.kernel.org,
	Eric Dumazet <eric.dumazet@...il.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>
Subject: Re: fs/stat: Reduce memory requirements for stat_open

On Thu, 12 Jun 2014, Stefan Bader wrote:

> doh, so you guys have been hit by that before. And I have missed the fact that
> single_open is special. Which makes the change for the upper limit do the wrong
> thing. While long-term it sounds like changing it to vmalloc or iterative reads
> sounds better, maybe the change from possible to online cpus might be something
> that is better acceptable as a quick fix... Not sure. At least this giving back
> a bit of attention to the matter and it is not only affecting zSeries. x86
> starts to see hw that requires a similar high possible cpus... :)
> 

Heiko's patches that should fix this problem are now in -mm, so it would 
be nice to know if there are any existing issues that haven't been 
addressed yet with your bug report.  See 
http://www.ozlabs.org/~akpm/mmotm/
--
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/