From: Jan Kara <jack@suse.cz>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Jan Kara <jack@suse.cz>,
stable@vger.kernel.org, Ted Tso <tytso@mit.edu>,
linux-ext4@vger.kernel.org
Subject: Re: Pick commit 2729cfdcfa ("ext4: use ext4_journal_start/stop for fast commit transactions")
Date: Fri, 28 Apr 2023 14:02:46 +0200 [thread overview]
Message-ID: <20230428120246.hzx6lhkvmfdspy75@quack3> (raw)
In-Reply-To: <2023042804-feed-radiantly-2a07@gregkh>
On Fri 28-04-23 09:32:34, Greg KH wrote:
> On Thu, Apr 27, 2023 at 06:24:59PM +0200, Jan Kara wrote:
> > Hello,
> >
> > recently I've debugged a deadlock issue in ext4 fast commit feature in our
> > openSUSE Leap kernel. Checking with upstream I've found out the issue was
> > accidentally fixed by commit 2729cfdcfa1c ("ext4: use
> > ext4_journal_start/stop for fast commit transactions"). Can you please pick
> > up this commit into the stable tree? The problem has been there since fast
> > commit began to exist (in 5.10-rc1) so 5.10 and 5.15 stable trees need the
> > fix. Thanks!
>
> This commit does not apply to those branches, so how was it tested?
Hum, I've picked up the patch to our 5.14-based distro kernel and it
applied (and passed testing) without issues so I was hoping 5.15 and 5.10
would work as well. Apparently I was wrong. Sorry for the trouble.
> Can you send us backported, and tested, versions of this commit so that
> we can apply them?
Yeah, I'll look into applying the patch directly to stable branches.
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2023-04-28 12:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-27 16:24 Pick commit 2729cfdcfa ("ext4: use ext4_journal_start/stop for fast commit transactions") Jan Kara
2023-04-28 7:32 ` Greg KH
2023-04-28 12:02 ` Jan Kara [this message]
2023-04-28 14:49 ` Jan Kara
2023-04-28 14:51 ` Jan Kara
2023-05-06 2:09 ` 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=20230428120246.hzx6lhkvmfdspy75@quack3 \
--to=jack@suse.cz \
--cc=gregkh@linuxfoundation.org \
--cc=linux-ext4@vger.kernel.org \
--cc=stable@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox