From: Greg KH <gregkh@linuxfoundation.org>
To: Tudor Ambarus <tudor.ambarus@linaro.org>
Cc: stable@vger.kernel.org, tytso@mit.edu, adilger.kernel@dilger.ca,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
joneslee@google.com
Subject: Re: [PATCH][for stable [4.14, 5.10] 0/3] ext4: fix use-after-free in ext4_xattr_set_entry
Date: Sun, 23 Apr 2023 15:22:35 +0200 [thread overview]
Message-ID: <2023042328-directed-quicken-e878@gregkh> (raw)
In-Reply-To: <20230419064610.1918038-1-tudor.ambarus@linaro.org>
On Wed, Apr 19, 2023 at 06:46:07AM +0000, Tudor Ambarus wrote:
> This is a good example that emphasizes that the order in which patches
> are queued to stable matters. More details in the revert commit.
> Tested and intended for 4.14, 4.19, 5.4, 5.10.
>
> Baokun Li (1):
> ext4: fix use-after-free in ext4_xattr_set_entry
>
> Ritesh Harjani (1):
> ext4: remove duplicate definition of ext4_xattr_ibody_inline_set()
>
> Tudor Ambarus (1):
> Revert "ext4: fix use-after-free in ext4_xattr_set_entry"
>
> fs/ext4/inline.c | 11 +++++------
> fs/ext4/xattr.c | 26 +-------------------------
> fs/ext4/xattr.h | 6 +++---
> 3 files changed, 9 insertions(+), 34 deletions(-)
All now queued up, thanks.
greg k-h
prev parent reply other threads:[~2023-04-23 13:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-19 6:46 [PATCH][for stable [4.14, 5.10] 0/3] ext4: fix use-after-free in ext4_xattr_set_entry Tudor Ambarus
2023-04-19 6:46 ` [PATCH][for stable [4.14, 5.10] 1/3] Revert "ext4: fix use-after-free in ext4_xattr_set_entry" Tudor Ambarus
2023-04-19 6:46 ` [PATCH][for stable [4.14, 5.10] 2/3] ext4: remove duplicate definition of ext4_xattr_ibody_inline_set() Tudor Ambarus
2023-04-19 6:46 ` [PATCH][for stable [4.14, 5.10] 3/3] ext4: fix use-after-free in ext4_xattr_set_entry Tudor Ambarus
2023-04-23 13:22 ` 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=2023042328-directed-quicken-e878@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=adilger.kernel@dilger.ca \
--cc=joneslee@google.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tudor.ambarus@linaro.org \
--cc=tytso@mit.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.