linux-kernel - Re: upcoming kerneloops.org item: get_page_from

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.LFD.2.01.0906281101030.3605@localhost.localdomain>
Date:	Sun, 28 Jun 2009 11:01:42 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Pavel Machek <pavel@....cz>
cc:	Andrew Morton <akpm@...ux-foundation.org>, penberg@...helsinki.fi,
	arjan@...radead.org, linux-kernel@...r.kernel.org,
	cl@...ux-foundation.org, npiggin@...e.de
Subject: Re: upcoming kerneloops.org item: get_page_from_freelist

On Sun, 28 Jun 2009, Pavel Machek wrote:
> 
> Ok, so we should re-add that 4MB buffer to suspend, so that
> allocations work even during that, right?

Pavel, you really are a one-trick pony, aren't you?

Give it up. Return to your pet worry when there are any actual reports. As 
you have been told several times.

The _other_ part of memory management that you and Andrew seem to be 
ignoring is that it's very robust, and keeps extra memory around, and just 
generally does the right thing. We don't generally pre-allocate anything, 
because we don't need to.

Almost the _only_ way to run out of memory is to have tons and tons of 
dirty pages around. Yes, it can happen. But if it happens, you're almost 
guaranteed to be screwed anyway. The whole VM is designed around the 
notion that most of memory is just clean caches, and it's designed around 
that simply because if it's not true, the VM freedom is so small that 
there's not a lot a VM can reasonably do.

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