linux-kernel - Re: [PATCH v2 1/2] mm, kasan: don't call kasan

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: <20160422143259.b2d2c253da7ea6fa4b425269@linux-foundation.org>
Date:	Fri, 22 Apr 2016 14:32:59 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Alexander Potapenko <glider@...gle.com>
Cc:	adech.fo@...il.com, dvyukov@...gle.com, cl@...ux.com,
	ryabinin.a.a@...il.com, kcc@...gle.com, kasan-dev@...glegroups.com,
	linux-kernel@...r.kernel.org, linux-mm@...ck.org
Subject: Re: [PATCH v2 1/2] mm, kasan: don't call kasan_krealloc() from
 ksize().

On Wed, 13 Apr 2016 13:20:09 +0200 Alexander Potapenko <glider@...gle.com> wrote:

> Instead of calling kasan_krealloc(), which replaces the memory allocation
> stack ID (if stack depot is used), just unpoison the whole memory chunk.

I don't understand why these two patches exist.  Bugfix?  Cleanup? 
Optimization?


I had to change kmalloc_tests_init() a bit due to
mm-kasan-initial-memory-quarantine-implementation.patch:

        kasan_stack_oob();
        kasan_global_oob();
 #ifdef CONFIG_SLAB
        kasan_quarantine_cache();
 #endif
+       ksize_unpoisons_memory();
        return -EAGAIN;
 }

Please check.