From: "Lin, Zhenpeng" <zplin@psu.edu>
To: Kees Cook <keescook@chromium.org>
Cc: Christoph Lameter <cl@linux.com>,
Pekka Enberg <penberg@kernel.org>,
David Rientjes <rientjes@google.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Andrew Morton <akpm@linux-foundation.org>,
Vlastimil Babka <vbabka@suse.cz>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] slub: choose the right freelist pointer location when creating small caches
Date: Tue, 8 Jun 2021 19:06:45 +0000 [thread overview]
Message-ID: <25AB8A72-B970-47C2-8688-48126075E72E@psu.edu> (raw)
In-Reply-To: <202106081140.F73F91F@keescook>
No problem. Just took a look and tested the patch, it looks good to me!
On 6/8/21, 2:41 PM, "Kees Cook" <keescook@chromium.org> wrote:
On Tue, Jun 08, 2021 at 06:33:01PM +0000, Lin, Zhenpeng wrote:
> There do exist objects whose size is smaller than 2*sizeof(void*). E.g. struct ccid in DCCP module.
Yes, sorry, I meant sizeof(void *). I've sent an updated v4 series and
CCed you. Are you able to test that and see if it fixes it for you too?
Thanks for the push to dust this series off again! :)
-Kees
--
Kees Cook
next prev parent reply other threads:[~2021-06-08 19:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-05 1:58 [PATCH] slub: choose the right freelist pointer location when creating small caches Lin, Zhenpeng
2021-06-08 18:26 ` Kees Cook
2021-06-08 18:33 ` Lin, Zhenpeng
2021-06-08 18:41 ` Kees Cook
2021-06-08 19:06 ` Lin, Zhenpeng [this message]
2021-06-08 23:14 ` Kees Cook
2021-06-10 20:20 ` Lin, Zhenpeng
2021-06-10 23:01 ` Kees Cook
2021-06-11 4:22 ` Lin, Zhenpeng
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=25AB8A72-B970-47C2-8688-48126075E72E@psu.edu \
--to=zplin@psu.edu \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=vbabka@suse.cz \
/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).