linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: "Lin, Zhenpeng" <zplin@psu.edu>
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: Thu, 10 Jun 2021 16:01:36 -0700	[thread overview]
Message-ID: <202106101601.E9273DD34@keescook> (raw)
In-Reply-To: <C7AC6780-9DCE-4CE5-90B1-9AA0731341BF@psu.edu>

On Thu, Jun 10, 2021 at 08:20:31PM +0000, Lin, Zhenpeng wrote:
> Sounds good. But I would suggest this to go to -stable as soon as possible. Because this bug is affecting the basic functionality of DCCP. It crashes kernel whenever a new socket in this module is created.

But only when redzoning is enabled, yes?

-- 
Kees Cook

  reply	other threads:[~2021-06-10 23:01 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
2021-06-08 23:14         ` Kees Cook
2021-06-10 20:20           ` Lin, Zhenpeng
2021-06-10 23:01             ` Kees Cook [this message]
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=202106101601.E9273DD34@keescook \
    --to=keescook@chromium.org \
    --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=vbabka@suse.cz \
    --cc=zplin@psu.edu \
    /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).