public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: hsimeliere.opensource@witekio.com
To: gregkh@linuxfoundation.org
Cc: andrii@kernel.org, ast@kernel.org, bruno.vernay@se.com,
	hsimeliere.opensource@witekio.com, stable@vger.kernel.org,
	xukuohai@huawei.com
Subject: Re: [PATCH v2 6.1] bpf: Prevent tail call between progs attached to different hooks
Date: Mon, 10 Feb 2025 17:32:33 +0100	[thread overview]
Message-ID: <20250210163233.6445-1-hsimeliere.opensource@witekio.com> (raw)
In-Reply-To: <2025021027-repaying-purveyor-9744@gregkh>

On Mon, Feb 10, 2025 at 10:55:07AM +0100, gregkh@linuxfoundation.org wrote:

> Never link to nvd, their "enhancements" are provably wrong and hurtful
> to the kernel ecosystem.  Always just refer to cve.org records or better
> yet, our own announcements.

Thank you for this information, I will take note of it for our next contribution.
So the CVE must be under a CNA or CISA score for the patch to be required by the kernel?  
Where can I find your own announcements? 

Thanks,
Hugo Simeliere

  parent reply	other threads:[~2025-02-10 16:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-10  8:40 [PATCH 6.1] bpf: Prevent tail call between progs attached to different hooks hsimeliere.opensource
2025-01-10 17:39 ` Sasha Levin
2025-01-12 11:51 ` Greg KH
2025-01-21 15:41   ` [PATCH v2 " hsimeliere.opensource
2025-01-21 17:09     ` Greg KH
2025-02-10  9:44       ` hsimeliere.opensource
2025-02-10  9:55         ` Greg KH
2025-02-10 14:29           ` hsimeliere.opensource
2025-02-10 14:43             ` Greg KH
2025-02-10 16:32           ` hsimeliere.opensource [this message]
2025-02-11  6:41             ` Greg KH
2025-01-21 19:52     ` Sasha Levin

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=20250210163233.6445-1-hsimeliere.opensource@witekio.com \
    --to=hsimeliere.opensource@witekio.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bruno.vernay@se.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=stable@vger.kernel.org \
    --cc=xukuohai@huawei.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