linux-security-module.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jarkko Sakkinen <jarkko@kernel.org>
To: Chen Ridong <chenridong@huaweicloud.com>,
	dhowells@redhat.com,  paul@paul-moore.com, jmorris@namei.org,
	serge@hallyn.com
Cc: keyrings@vger.kernel.org, linux-security-module@vger.kernel.org,
	 linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] security/keys: fix slab-out-of-bounds in key_task_permission
Date: Thu, 17 Oct 2024 11:39:14 +0300	[thread overview]
Message-ID: <cf01c9be92e9c5f4bbb970a37d38c7f3d1c29623.camel@kernel.org> (raw)
In-Reply-To: <912228e4-ca24-4ff1-9b18-af314b53835a@huaweicloud.com>

On Thu, 2024-10-17 at 09:19 +0800, Chen Ridong wrote:
> 
> 
> On 2024/10/16 13:14, Jarkko Sakkinen wrote:
> > On Wed, 2024-10-16 at 08:08 +0300, Jarkko Sakkinen wrote:
> > > > Friendly ping.
> > > 
> > > Thanks for pinging because I actually accidentally missed the
> > > original
> > > email!
> > > 
> > > Reviewed-by: Jarkko Sakkinen <jarkko@kernel.org>
> > > 
> > > I'll pick this up.
> > 
> > I tuned the commit message just a bit (see my comment
> > embedded):
> > 
> > https://git.kernel.org/pub/scm/linux/kernel/git/jarkko/linux-tpmdd.git/commit/?id=9bb3ba75c1c8fd8c9f6a0b1fd6409b725583a3e0
> > 
> > BR, Jarkko
> 
> Thanks you very much.

Thanks to you for patience with my earlier shitty reviews ;-) That was 
tbh the main issue with this bug fix getting through...

> Best regards,
> Ridong

BR, Jarkko

      reply	other threads:[~2024-10-17  8:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-08 12:46 [PATCH v2] security/keys: fix slab-out-of-bounds in key_task_permission Chen Ridong
2024-10-16  1:33 ` Chen Ridong
2024-10-16  5:08   ` Jarkko Sakkinen
2024-10-16  5:14     ` Jarkko Sakkinen
2024-10-17  1:19       ` Chen Ridong
2024-10-17  8:39         ` 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=cf01c9be92e9c5f4bbb970a37d38c7f3d1c29623.camel@kernel.org \
    --to=jarkko@kernel.org \
    --cc=chenridong@huaweicloud.com \
    --cc=dhowells@redhat.com \
    --cc=jmorris@namei.org \
    --cc=keyrings@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=paul@paul-moore.com \
    --cc=serge@hallyn.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).