[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20160712130201.9339f7dbc9575d2c0cb31aeb@linux-foundation.org>
Date: Tue, 12 Jul 2016 13:02:01 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Alexander Potapenko <glider@...gle.com>
Cc: adech.fo@...il.com, cl@...ux.com, dvyukov@...gle.com,
rostedt@...dmis.org, iamjoonsoo.kim@....com, js1304@...il.com,
kcc@...gle.com, aryabinin@...tuozzo.com, kuthonuzo.luruo@....com,
kasan-dev@...glegroups.com, linux-mm@...ck.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v7 1/2] mm, kasan: account for object redzone in SLUB's
nearest_obj()
On Tue, 12 Jul 2016 20:12:44 +0200 Alexander Potapenko <glider@...gle.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.
Powered by blists - more mailing lists