[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20150325145523.94d1033b93cd5c1010df93bf@linux-foundation.org>
Date: Wed, 25 Mar 2015 14:55:23 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: David Rientjes <rientjes@...gle.com>
Cc: Dave Kleikamp <shaggy@...nel.org>, Christoph Hellwig <hch@....de>,
Sebastian Ott <sebott@...ux.vnet.ibm.com>,
Mikulas Patocka <mpatocka@...hat.com>,
Catalin Marinas <catalin.marinas@....com>,
linux-kernel@...r.kernel.org, linux-mm@...ck.org,
jfs-discussion@...ts.sourceforge.net,
Andrey Ryabinin <a.ryabinin@...sung.com>
Subject: Re: [patch v2 4/4] mm, mempool: poison elements backed by page
allocator
On Tue, 24 Mar 2015 16:10:01 -0700 (PDT) David Rientjes <rientjes@...gle.com> wrote:
> Elements backed by the slab allocator are poisoned when added to a
> mempool's reserved pool.
>
> It is also possible to poison elements backed by the page allocator
> because the mempool layer knows the allocation order.
>
> This patch extends mempool element poisoning to include memory backed by
> the page allocator.
>
> This is only effective for configs with CONFIG_DEBUG_SLAB or
> CONFIG_SLUB_DEBUG_ON.
>
Maybe mempools should get KASAN treatment (as well as this)?
--
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/
Powered by blists - more mailing lists