linux-kernel - Re: quicklists confuse meminfo

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: <Pine.LNX.4.64.0803100855110.23575@schroedinger.engr.sgi.com>
Date:	Mon, 10 Mar 2008 08:55:41 -0700 (PDT)
From:	Christoph Lameter <clameter@....com>
To:	Ingo Molnar <mingo@...e.hu>
cc:	Arjan van de Ven <arjan@...radead.org>,
	KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	LKML <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Bart Van Assche <bart.vanassche@...il.com>
Subject: Re: quicklists confuse meminfo

On Sun, 9 Mar 2008, Ingo Molnar wrote:

> > careful with this; the quicklists aren't JUST for speed they are also 
> > there to make sure a page we free that is a pagetable, is not reused 
> > until we have finished flushing the tlbs on all the cpus that saw it. 
> > This is a really hard correctness requirement, and while I can see 
> > that quicklists are probably not the best way to achieve this, we 
> > can't just throw away the behavior ;(
> 
> no, that's not true anymore - and the current quicklists code doesnt do 
> anything like that AFAICS. It used to be a lot more complex, but now 
> it's just a thin wrapper around the page allocator.

Sure it does that. It interacts with the TLB logic which is another bad 
thing as Linus has pointed out.


--
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/