From: Christopher Lameter <cl@linux.com>
To: Marco Elver <elver@google.com>
Cc: linux-kernel@vger.kernel.org,
Andrey Ryabinin <aryabinin@virtuozzo.com>,
Dmitry Vyukov <dvyukov@google.com>,
Alexander Potapenko <glider@google.com>,
Andrey Konovalov <andreyknvl@google.com>,
Pekka Enberg <penberg@kernel.org>,
David Rientjes <rientjes@google.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Andrew Morton <akpm@linux-foundation.org>,
Mark Rutland <mark.rutland@arm.com>,
kasan-dev@googlegroups.com, linux-mm@kvack.org
Subject: Re: [PATCH v5 4/5] mm/slab: Refactor common ksize KASAN logic into slab_common.c
Date: Mon, 8 Jul 2019 20:20:56 +0000 [thread overview]
Message-ID: <0100016bd33f19f3-46ea67c2-d930-4e22-9934-41d6b25d5bd5-000000@email.amazonses.com> (raw)
In-Reply-To: <20190708170706.174189-5-elver@google.com>
On Mon, 8 Jul 2019, Marco Elver wrote:
> This refactors common code of ksize() between the various allocators
> into slab_common.c: __ksize() is the allocator-specific implementation
> without instrumentation, whereas ksize() includes the required KASAN
> logic.
Acked-by: Christoph Lameter <cl@linux.com>
next prev parent reply other threads:[~2019-07-08 20:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-08 17:07 [PATCH v5 0/5] Add object validation in ksize() Marco Elver
2019-07-08 17:07 ` [PATCH v5 1/5] mm/kasan: Introduce __kasan_check_{read,write} Marco Elver
2019-07-08 17:07 ` [PATCH v5 2/5] mm/kasan: Change kasan_check_{read,write} to return boolean Marco Elver
2019-07-08 17:07 ` [PATCH v5 3/5] lib/test_kasan: Add test for double-kzfree detection Marco Elver
2019-07-08 17:07 ` [PATCH v5 4/5] mm/slab: Refactor common ksize KASAN logic into slab_common.c Marco Elver
2019-07-08 20:20 ` Christopher Lameter [this message]
2019-07-08 17:07 ` [PATCH v5 5/5] mm/kasan: Add object validation in ksize() Marco Elver
2019-07-10 18:29 ` [PATCH v5 0/5] " Andrey Ryabinin
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=0100016bd33f19f3-46ea67c2-d930-4e22-9934-41d6b25d5bd5-000000@email.amazonses.com \
--to=cl@linux.com \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@google.com \
--cc=aryabinin@virtuozzo.com \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mark.rutland@arm.com \
--cc=penberg@kernel.org \
--cc=rientjes@google.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;
as well as URLs for NNTP newsgroup(s).