linux-kernel - Re: [RFC] slub memory quarantine

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]

Date:	Tue, 03 Mar 2015 18:39:56 +0300
From:	Andrey Ryabinin <a.ryabinin@...sung.com>
To:	Dmitry Vyukov <dvyukov@...gle.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Christoph Lameter <cl@...ux.com>,
	David Rientjes <rientjes@...gle.com>,
	Joonsoo Kim <iamjoonsoo.kim@....com>,
	Pekka Enberg <penberg@...nel.org>,
	Linux Memory Management List <linux-mm@...ck.org>,
	Sasha Levin <sasha.levin@...cle.com>,
	Dmitry Chernenkov <dmitryc@...gle.com>,
	Konstantin Khlebnikov <koct9i@...il.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [RFC] slub memory quarantine

On 03/03/2015 12:10 PM, Dmitry Vyukov wrote:
> Please hold on with this.
> Dmitry Chernenkov is working on a quarantine that works with both slub
> and slab, does not cause spurious OOMs and does not depend on
> slub-debug which has unacceptable performance (acquires global lock).

I think that it's a separate issue. KASan already depend on slub_debug - it required for redzones/user tracking.
I think that some parts slub debugging (like user tracking and this quarantine)
could be moved (for CONFIG_KASAN=y) to the fast path without any locking.


> Me or Dmitry C will send an email to kasan-dev@...glegroups.com to
> discuss quarantine development direction.
> 



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