From: Greg KH <greg@kroah.com>
To: hsimeliere.opensource@witekio.com
Cc: stable@vger.kernel.org, Miklos Szeredi <mszeredi@redhat.com>,
James Morris <jamorris@linux.microsoft.com>
Subject: Re: [PATCH 4.19 1/1] vfs: move cap_convert_nscap() call into vfs_setxattr()
Date: Thu, 29 Aug 2024 18:33:47 +0200 [thread overview]
Message-ID: <2024082914-relay-climatic-95c7@gregkh> (raw)
In-Reply-To: <20240829162631.19391-2-hsimeliere.opensource@witekio.com>
On Thu, Aug 29, 2024 at 06:26:21PM +0200, hsimeliere.opensource@witekio.com wrote:
> From: Miklos Szeredi <mszeredi@redhat.com>
>
> commit 7c03e2cda4a584cadc398e8f6641ca9988a39d52 upstream.
>
> cap_convert_nscap() does permission checking as well as conversion of the
> xattr value conditionally based on fs's user-ns.
>
> This is needed by overlayfs and probably other layered fs (ecryptfs) and is
> what vfs_foo() is supposed to do anyway.
>
> Signed-off-by: Miklos Szeredi <mszeredi@redhat.com>
> Acked-by: James Morris <jamorris@linux.microsoft.com>
> Signed-off-by: Hugo SIMELIERE <hsimeliere.opensource@witekio.com>
> ---
> fs/xattr.c | 17 +++++++++++------
> include/linux/capability.h | 2 +-
> security/commoncap.c | 3 +--
> 3 files changed, 13 insertions(+), 9 deletions(-)
Again, we can not take chagnes for only older kernels and not newer
ones. Please resend for all applicable releases.
thanks,
greg k-h
next prev parent reply other threads:[~2024-08-29 16:33 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 [this message]
2024-08-29 16:53 ` hsimeliere.opensource
2024-08-29 16:57 ` Greg KH
2024-08-29 16:35 ` [PATCH 4.19 0/1] Fix CVE-2021-3493 Greg KH
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=2024082914-relay-climatic-95c7@gregkh \
--to=greg@kroah.com \
--cc=hsimeliere.opensource@witekio.com \
--cc=jamorris@linux.microsoft.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