From: Andrew Morton <akpm@linux-foundation.org>
To: Alexander Potapenko <glider@google.com>
Cc: adech.fo@gmail.com, cl@linux.com, dvyukov@google.com,
rostedt@goodmis.org, iamjoonsoo.kim@lge.com, js1304@gmail.com,
kcc@google.com, aryabinin@virtuozzo.com, kuthonuzo.luruo@hpe.com,
kasan-dev@googlegroups.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 1/2] mm, kasan: account for object redzone in SLUB's nearest_obj()
Date: Tue, 12 Jul 2016 13:02:01 -0700 [thread overview]
Message-ID: <20160712130201.9339f7dbc9575d2c0cb31aeb@linux-foundation.org> (raw)
In-Reply-To: <1468347165-41906-2-git-send-email-glider@google.com>
On Tue, 12 Jul 2016 20:12:44 +0200 Alexander Potapenko <glider@google.com> wrote:
> When looking up the nearest SLUB object for a given address, correctly
> calculate its offset if SLAB_RED_ZONE is enabled for that cache.
What are the runtime effects of this fix? Please always include this
info when fixing bugs so that others can decide which kernel(s) need
patching.
--
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>
next prev parent reply other threads:[~2016-07-12 20:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-12 18:12 [PATCH v7 0/2] mm, kasan: stackdepot and quarantine for SLUB Alexander Potapenko
2016-07-12 18:12 ` [PATCH v7 1/2] mm, kasan: account for object redzone in SLUB's nearest_obj() Alexander Potapenko
2016-07-12 20:02 ` Andrew Morton [this message]
2016-07-13 12:14 ` Alexander Potapenko
2016-07-12 18:12 ` [PATCH v7 2/2] mm, kasan: switch SLUB to stackdepot, enable memory quarantine for SLUB Alexander Potapenko
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=20160712130201.9339f7dbc9575d2c0cb31aeb@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=adech.fo@gmail.com \
--cc=aryabinin@virtuozzo.com \
--cc=cl@linux.com \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=js1304@gmail.com \
--cc=kasan-dev@googlegroups.com \
--cc=kcc@google.com \
--cc=kuthonuzo.luruo@hpe.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rostedt@goodmis.org \
/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;
as well as URLs for NNTP newsgroup(s).