public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: hsimeliere.opensource@witekio.com
Cc: stable@vger.kernel.org
Subject: Re: [PATCH 4.19 0/1] Fix CVE-2021-3493
Date: Thu, 29 Aug 2024 18:35:25 +0200	[thread overview]
Message-ID: <2024082943-sprinkled-stinky-46d1@gregkh> (raw)
In-Reply-To: <20240829162631.19391-1-hsimeliere.opensource@witekio.com>

On Thu, Aug 29, 2024 at 06:26:20PM +0200, hsimeliere.opensource@witekio.com wrote:
> 
> https://nvd.nist.gov/vuln/detail/CVE-2021-3493
> 

This "bug" was only applicable to Ubuntu kernel releases, why are you
thinking that it should be backported to kernel.org releases?

Please only send us fixes that are relevant for our kernel trees.

thanks,

greg k-h

      parent reply	other threads:[~2024-08-29 16:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-29 16:26 [PATCH 4.19 0/1] Fix CVE-2021-3493 hsimeliere.opensource
2024-08-29 16:26 ` [PATCH 4.19 1/1] vfs: move cap_convert_nscap() call into vfs_setxattr() hsimeliere.opensource
2024-08-29 16:33   ` Greg KH
2024-08-29 16:53     ` hsimeliere.opensource
2024-08-29 16:57       ` Greg KH
2024-08-29 16:35 ` Greg KH [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=2024082943-sprinkled-stinky-46d1@gregkh \
    --to=greg@kroah.com \
    --cc=hsimeliere.opensource@witekio.com \
    --cc=stable@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