public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: hsimeliere.opensource@witekio.com
Cc: stable@vger.kernel.org, Miklos Szeredi <mszeredi@redhat.com>
Subject: Re: [PATCH 4.19 1/6] ovl: check permission to open real file
Date: Thu, 29 Aug 2024 18:17:07 +0200	[thread overview]
Message-ID: <2024082904-unmarked-audacity-34dd@gregkh> (raw)
In-Reply-To: <20240829151732.14930-1-hsimeliere.opensource@witekio.com>

On Thu, Aug 29, 2024 at 05:17:00PM +0200, hsimeliere.opensource@witekio.com wrote:
> From: Miklos Szeredi <mszeredi@redhat.com>
> 
> commit 05acefb4872dae89e772729efb194af754c877e8 upstream.

<snip>

For obvious reasons we can not take a backport to an older kernel tree
and not all newer ones as well, otherwise you would upgrade and have a
regression.  I think it says that in the documentation as well
somewhere...

Please create patch series for all currently maintained kernel trees if
you wish to have stuff like this merged, and resend them.

thanks,

greg k-h

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

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-29 15:17 [PATCH 4.19 1/6] ovl: check permission to open real file hsimeliere.opensource
2024-08-29 15:17 ` [PATCH 4.19 2/6] ovl: verify permissions in ovl_path_open() hsimeliere.opensource
2024-08-29 15:17 ` [PATCH 4.19 3/6] ovl: switch to mounter creds in readdir hsimeliere.opensource
2024-08-29 15:17 ` [PATCH 4.19 4/6] ovl: do not fail because of O_NOATIME hsimeliere.opensource
2024-08-29 15:17 ` [PATCH 4.19 5/6] ovl: pass correct flags for opening real directory hsimeliere.opensource
2024-08-29 15:17 ` [PATCH 4.19 6/6] ovl: call secutiry hook in ovl_real_ioctl() hsimeliere.opensource
2024-08-29 15:43   ` This series of patches fixes this CVE: CVE-2020-16120 https://nvd.nist.gov/vuln/detail/CVE-2020-16120 hsimeliere.opensource
2024-08-29 16:17 ` 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=2024082904-unmarked-audacity-34dd@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=hsimeliere.opensource@witekio.com \
    --cc=mszeredi@redhat.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