Received-SPF: pass (google.com: domain of linux-ext4-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Fri, 28 Apr 2023 14:02:46 +0200
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")
Message-ID: <20230428120246.hzx6lhkvmfdspy75@quack3>
References: <20230427162459.qb3tnh3be6ofibzz@quack3>
 <2023042804-feed-radiantly-2a07@gregkh>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <2023042804-feed-radiantly-2a07@gregkh>
Precedence: bulk

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