From: Joonsoo Kim <js1304@gmail.com>
To: Andrey Ryabinin <ryabinin.a.a@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Christoph Lameter <cl@linux.com>,
Pekka Enberg <penberg@kernel.org>,
David Rientjes <rientjes@google.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>
Subject: Re: [PATCH v2] mm/slub: support left redzone
Date: Sat, 27 Feb 2016 02:08:35 +0900 [thread overview]
Message-ID: <CAAmzW4MH3EmnXCmz-n=qYGPXZhrajVYOCkNw_0XvhnOK=T9-Ng@mail.gmail.com> (raw)
In-Reply-To: <CAPAsAGytHfMaX8VzgWX-PBXcH8aO0G82L3ZX5dSNa=trBFVsyg@mail.gmail.com>
2016-02-27 1:47 GMT+09:00 Andrey Ryabinin <ryabinin.a.a@gmail.com>:
> 2016-02-26 7:36 GMT+03:00 <js1304@gmail.com>:
>> From: Joonsoo Kim <iamjoonsoo.kim@lge.com>
>>
>> SLUB already has a redzone debugging feature. But it is only positioned
>> at the end of object (aka right redzone) so it cannot catch left oob.
>> Although current object's right redzone acts as left redzone of next
>> object, first object in a slab cannot take advantage of this effect. This
>> patch explicitly adds a left red zone to each object to detect left oob
>> more precisely.
>>
>
> So why for each object? Can't we have left redzone only for the first object?
It's easier to implement and less code churn than allowing left redzone
only for the first object.
Thanks.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2016-02-26 17:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-26 4:36 js1304
2016-02-26 16:47 ` Andrey Ryabinin
2016-02-26 17:08 ` Joonsoo Kim [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAAmzW4MH3EmnXCmz-n=qYGPXZhrajVYOCkNw_0XvhnOK=T9-Ng@mail.gmail.com' \
--to=js1304@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=ryabinin.a.a@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox