Re: [PATCH mm v3 18/19] kasan, mm: allow cache merging with no metadata

2020-11-23 Thread Andrey Konovalov
On Tue, Nov 17, 2020 at 2:25 PM Dmitry Vyukov wrote: > > On Fri, Nov 13, 2020 at 11:20 PM Andrey Konovalov > wrote: > > > > The reason cache merging is disabled with KASAN is because KASAN puts its > > metadata right after the allocated object. When the merged caches have > > slightly different

Re: [PATCH mm v3 18/19] kasan, mm: allow cache merging with no metadata

2020-11-17 Thread Dmitry Vyukov
On Fri, Nov 13, 2020 at 11:20 PM Andrey Konovalov wrote: > > The reason cache merging is disabled with KASAN is because KASAN puts its > metadata right after the allocated object. When the merged caches have > slightly different sizes, the metadata ends up in different places, which > KASAN

Re: [PATCH mm v3 18/19] kasan, mm: allow cache merging with no metadata

2020-11-16 Thread Marco Elver
On Fri, Nov 13, 2020 at 11:20PM +0100, Andrey Konovalov wrote: > The reason cache merging is disabled with KASAN is because KASAN puts its > metadata right after the allocated object. When the merged caches have > slightly different sizes, the metadata ends up in different places, which > KASAN

[PATCH mm v3 18/19] kasan, mm: allow cache merging with no metadata

2020-11-13 Thread Andrey Konovalov
The reason cache merging is disabled with KASAN is because KASAN puts its metadata right after the allocated object. When the merged caches have slightly different sizes, the metadata ends up in different places, which KASAN doesn't support. It might be possible to adjust the metadata allocation