mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Siddh Raman Pant <siddh.raman.pant@oracle.com>
To: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Cc: "cve@kernel.org" <cve@kernel.org>,
	"linux-cve-announce@vger.kernel.org"
	<linux-cve-announce@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [External] : Re: CVE-2024-26920: tracing/trigger: Fix to return error if failed to alloc snapshot
Date: Fri, 19 Apr 2024 08:23:17 +0000	[thread overview]
Message-ID: <1263c5636be781504b91809a98760001247d0346.camel@oracle.com> (raw)
In-Reply-To: <2024041811-freeing-licking-bd94@gregkh>

[-- Attachment #1: Type: text/plain, Size: 555 bytes --]

On Thu, Apr 18 2024 at 15:13:40 +0200, gregkh@linuxfoundation.org
wrote:
> > > Should we just take that patch instead?
> > 
> > The series in which the patch is posted is here:
> > [...]
> > 
> > Seems like some good tracing subsystem refactoring. So if I understand
> > Documentation/process/stable-kernel-rules.rst correctly, I would say we
> > should not.
> 
> So the documentation on the commit here is wrong (i.e. wrong Fixes:
> tag?)  If so, that needs to be said somewhere...

Yes, the Fixes tag seems to be wrong.

Thanks,
Siddh

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2024-04-19  8:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2024041738-CVE-2024-26920-a681@gregkh>
2024-04-18 11:59 ` Siddh Raman Pant
2024-04-18 12:34   ` gregkh
2024-04-18 13:06     ` [External] : " Siddh Raman Pant
2024-04-18 13:13       ` gregkh
2024-04-19  8:23         ` Siddh Raman Pant [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=1263c5636be781504b91809a98760001247d0346.camel@oracle.com \
    --to=siddh.raman.pant@oracle.com \
    --cc=cve@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-cve-announce@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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
all inboxes | Powered by JetHome®