From: Greg KH <gregkh@linuxfoundation.org>
To: fdmanana@kernel.org
Cc: linux-btrfs@vger.kernel.org, erosca@de.adit-jv.com,
Maksim.Paimushkin@se.bosch.com, Matthias.Thomae@de.bosch.com,
Sebastian.Unger@bosch.com, Dirk.Behme@de.bosch.com,
Eugeniu.Rosca@bosch.com, wqu@suse.com, dsterba@suse.com,
stable@vger.kernel.org, Filipe Manana <fdmanana@suse.com>
Subject: Re: [PATCH 0/4 for 5.15 stable] btrfs: some directory fixes for stable 5.15
Date: Fri, 26 Jan 2024 17:15:11 -0800 [thread overview]
Message-ID: <2024012633-retold-avid-8113@gregkh> (raw)
In-Reply-To: <cover.1706183427.git.fdmanana@suse.com>
On Thu, Jan 25, 2024 at 11:59:34AM +0000, fdmanana@kernel.org wrote:
> From: Filipe Manana <fdmanana@suse.com>
>
> Here follows the backport of some directory related fixes for the stable
> 5.15 tree. I tested these on top of 5.15.147.
As these are not also in 6.1.y, we can't take these as you do not want
to upgrade and have regressions, right?
If you can provide a working set of 6.1.y changes for these, we will be
glad to queue them all up, thanks.
greg k-h
next prev parent reply other threads:[~2024-01-27 1:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 11:59 [PATCH 0/4 for 5.15 stable] btrfs: some directory fixes for stable 5.15 fdmanana
2024-01-25 11:59 ` [PATCH 1/4 for 5.15 stable] btrfs: fix infinite directory reads fdmanana
2024-01-26 19:06 ` Eugeniu Rosca
2024-01-25 11:59 ` [PATCH 2/4 for 5.15 stable] btrfs: set last dir index to the current last index when opening dir fdmanana
2024-01-26 19:07 ` Eugeniu Rosca
2024-01-25 11:59 ` [PATCH 3/4 for 5.15 stable] btrfs: refresh dir last index during a rewinddir(3) call fdmanana
2024-01-26 19:08 ` Eugeniu Rosca
2024-01-25 11:59 ` [PATCH 4/4 for 5.15 stable] btrfs: fix race between reading a directory and adding entries to it fdmanana
2024-01-26 19:09 ` Eugeniu Rosca
2024-01-26 18:55 ` [PATCH 0/4 for 5.15 stable] btrfs: some directory fixes for stable 5.15 Eugeniu Rosca
2024-01-27 18:02 ` Filipe Manana
2024-01-29 13:39 ` Eugeniu Rosca
2024-01-27 1:15 ` Greg KH [this message]
2024-01-27 17:58 ` Filipe Manana
2024-01-27 18:18 ` Filipe Manana
2024-01-27 21:19 ` 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=2024012633-retold-avid-8113@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=Dirk.Behme@de.bosch.com \
--cc=Eugeniu.Rosca@bosch.com \
--cc=Maksim.Paimushkin@se.bosch.com \
--cc=Matthias.Thomae@de.bosch.com \
--cc=Sebastian.Unger@bosch.com \
--cc=dsterba@suse.com \
--cc=erosca@de.adit-jv.com \
--cc=fdmanana@kernel.org \
--cc=fdmanana@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=wqu@suse.com \
/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