The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Jarkko Sakkinen <jarkko@kernel.org>
To: Mohammed EL Kadiri <med08elkadiri@gmail.com>
Cc: "Vlastimil Babka (SUSE)" <vbabka@kernel.org>,
	David Howells <dhowells@redhat.com>,
	Paul Moore <paul@paul-moore.com>,
	James Morris <jmorris@namei.org>,
	"Serge E . Hallyn" <serge@hallyn.com>,
	Kees Cook <kees@kernel.org>, Vlastimil Babka <vbabka@suse.cz>,
	keyrings@vger.kernel.org, linux-security-module@vger.kernel.org,
	linux-hardening@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] keys: prevent slab cache merging for key_jar
Date: Tue, 9 Jun 2026 18:36:24 +0300	[thread overview]
Message-ID: <aigy-NpXyLrESpv-@kernel.org> (raw)
In-Reply-To: <CAAMeuQTue5bkbhjYLjsRCnB9=KBifsPNQ=ZRVp+wCh2TiXE7Uw@mail.gmail.com>

On Tue, Jun 09, 2026 at 04:15:18PM +0100, Mohammed EL Kadiri wrote:
> Hi Jarkko, Vlastimil,
> 
> I will send a v2 this evening with the commit message reworked. I will
> remove CVE references and frame it as hardening rather than an active
> vulnerability. I'll also drop the inaccurate skbuff_head_cache
> comparison that Vlastimil flagged.
> 
> No need to strip it yourself, I'll have it out today.

Take your time :-) And thanks Vlastimil for the remark!

If I get the patch within this week, all is fine.

> 
> Thanks,
> Mohammed

BR, Jarkko

      reply	other threads:[~2026-06-09 15:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-04 12:50 [PATCH] keys: prevent slab cache merging for key_jar Mohammed EL Kadiri
2026-06-05 12:16 ` Vlastimil Babka (SUSE)
2026-06-08  4:27   ` Jarkko Sakkinen
2026-06-08  4:22 ` Jarkko Sakkinen
2026-06-08  7:20   ` Vlastimil Babka (SUSE)
2026-06-09 14:52     ` Jarkko Sakkinen
2026-06-09 15:15       ` Mohammed EL Kadiri
2026-06-09 15:36         ` Jarkko Sakkinen [this message]

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=aigy-NpXyLrESpv-@kernel.org \
    --to=jarkko@kernel.org \
    --cc=dhowells@redhat.com \
    --cc=jmorris@namei.org \
    --cc=kees@kernel.org \
    --cc=keyrings@vger.kernel.org \
    --cc=linux-hardening@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=med08elkadiri@gmail.com \
    --cc=paul@paul-moore.com \
    --cc=serge@hallyn.com \
    --cc=vbabka@kernel.org \
    --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