linux-kernel - [RFC][PATCH 0/3] track pte pages and use in OOM score

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-next>] [day] [month] [year] [list]

Date:	Fri, 15 Apr 2011 10:38:21 -0700
From:	Dave Hansen <dave@...ux.vnet.ibm.com>
To:	linux-kernel@...r.kernel.org
Cc:	linux-mm@...ck.org, Dave Hansen <dave@...ux.vnet.ibm.com>
Subject: [RFC][PATCH 0/3] track pte pages and use in OOM score

PTE pages are a relatively invisible memory user.  Neither users
nor the kernel have any way of telling how many of them any given
application is using.  Nefarious applications can also
potentially tie up lagre amounts of memory in them:

	foo = malloc(big);
	touch(foo);
	madvise(foo, big, MADV_DONTNEED);

That'll leave you with no RSS for "foo", but the pagetable pages
will still be there.  Do that enough times, and you can
potentially harm the system.  Even worse, the OOM killer will not
necessarily go after such an application since the kernel has no
record of the pages.

For the containers and OpenVZ folks, pte pages are one of the
main consumers of kernel memory.  They should be able to use this
code as well.
--
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/