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.1406251551460.4592@chino.kir.corp.google.com>
Date:	Wed, 25 Jun 2014 15:52:30 -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 Wed, 25 Jun 2014, Stefan Bader wrote:

> Heiko and I both had the same issue. Since some x86 hardware also reaches a lot
> of CPUs (hyperthreads included), we bumped the possible number of CPUs to 256 at
> least for the 64bit kernel. And that resulted in failed accesses to /proc/stat
> when memory became fragmented.
> So the first patch will avoid this on most systems. I have not seen this myself,
> but I would expect him to be happy with 1/2 already. For really excessive
> hardware 2/2 will close the gap.
> Since this is no critical bug, I am fine with 3.17, too. I have not done so,
> yet, but I could let our reporter try the patches (again, probably not verifying
> the second part). Just waited to do so to see whether the code settles down to
> these changes.
> 

Ok, thanks.  Looks like

proc-stat-convert-to-single_open_size.patch
fs-seq_file-fallback-to-vmalloc-allocation.patch

are destined for 3.17.
--
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/