[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <2023042328-directed-quicken-e878@gregkh>
Date: Sun, 23 Apr 2023 15:22:35 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: Tudor Ambarus <tudor.ambarus@...aro.org>
Cc: stable@...r.kernel.org, tytso@....edu, adilger.kernel@...ger.ca,
linux-ext4@...r.kernel.org, linux-kernel@...r.kernel.org,
joneslee@...gle.com
Subject: Re: [PATCH][for stable [4.14, 5.10] 0/3] ext4: fix use-after-free in
ext4_xattr_set_entry
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
Powered by blists - more mailing lists