linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Dan Carpenter <dan.carpenter@linaro.org>
Cc: Naresh Kamboju <naresh.kamboju@linaro.org>,
	Zhang Yi <yi.zhang@huaweicloud.com>,
	stable@vger.kernel.org, patches@lists.linux.dev,
	linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
	akpm@linux-foundation.org, linux@roeck-us.net, shuah@kernel.org,
	patches@kernelci.org, lkft-triage@lists.linaro.org,
	pavel@denx.de, jonathanh@nvidia.com, f.fainelli@gmail.com,
	sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de,
	conor@kernel.org, hargar@microsoft.com, broonie@kernel.org,
	achill@achill.org, linux-ext4 <linux-ext4@vger.kernel.org>,
	linux-fsdevel@vger.kernel.org, Joseph Qi <jiangqi903@gmail.com>,
	Jan Kara <jack@suse.cz>, Theodore Ts'o <tytso@mit.edu>,
	Anders Roxell <anders.roxell@linaro.org>,
	Arnd Bergmann <arnd@arndb.de>,
	Ben Copeland <benjamin.copeland@linaro.org>
Subject: Re: [PATCH 6.16 000/564] 6.16.2-rc2 review
Date: Fri, 22 Aug 2025 14:14:10 +0200	[thread overview]
Message-ID: <2025082242-skyward-mascot-f992@gregkh> (raw)
In-Reply-To: <aKg41GMffk9t1p56@stanley.mountain>

On Fri, Aug 22, 2025 at 12:31:00PM +0300, Dan Carpenter wrote:
> On Wed, Aug 20, 2025 at 08:06:01PM +0530, Naresh Kamboju wrote:
> > On Tue, 19 Aug 2025 at 18:02, Greg Kroah-Hartman
> > <gregkh@linuxfoundation.org> wrote:
> > >
> > > This is the start of the stable review cycle for the 6.16.2 release.
> > > There are 564 patches in this series, all will be posted as a response
> > > to this one.  If anyone has any issues with these being applied, please
> > > let me know.
> > >
> > > Responses should be made by Thu, 21 Aug 2025 12:27:23 +0000.
> > > Anything received after that time might be too late.
> > >
> > > The whole patch series can be found in one patch at:
> > >         https://www.kernel.org/pub/linux/kernel/v6.x/stable-review/patch-6.16.2-rc2.gz
> > > or in the git tree and branch at:
> > >         git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-6.16.y
> > > and the diffstat can be found below.
> > >
> > > thanks,
> > >
> > > greg k-h
> > 
> > As I have reported last week on 6.16.1-rc1 as regression is
> > still noticed on 6.16.2-rc2.
> > 
> > WARNING: CPU: 0 PID: 7012 at fs/jbd2/transaction.c:334 start_this_handle
> > 
> > Full test log:
> > ------------[ cut here ]------------
> > [  153.965287] WARNING: CPU: 0 PID: 7012 at fs/jbd2/transaction.c:334
> > start_this_handle+0x4df/0x500
> 
> The problem is that we only applied the last two patches in:
> https://lore.kernel.org/linux-ext4/20250707140814.542883-1-yi.zhang@huaweicloud.com/
> 
> Naresh is on vacation until Monday, but he tested the patchset on
> linux-next and it fixed the issues.  So we need to cherry-pick the
> following commits.
> 
> 1bfe6354e097 ext4: process folios writeback in bytes
> f922c8c2461b ext4: move the calculation of wbc->nr_to_write to mpage_folio_done()
> ded2d726a304 ext4: fix stale data if it bail out of the extents mapping loop
> 2bddafea3d0d ext4: refactor the block allocation process of ext4_page_mkwrite()
> e2c4c49dee64 ext4: restart handle if credits are insufficient during allocating blocks
> 6b132759b0fe ext4: enhance tracepoints during the folios writeback
> 95ad8ee45cdb ext4: correct the reserved credits for extent conversion
> bbbf150f3f85 ext4: reserved credits for one extent during the folio writeback
> 57661f28756c ext4: replace ext4_writepage_trans_blocks()
> 
> They all apply cleanly to 6.16.3-rc1.

Ugh.  Ok, let me go push out a -rc for JUST this issue now so that
people can test and I can get it released for those that are tripped up
by it.  Thanks for the information, much appreciated.

greg k-h

  reply	other threads:[~2025-08-22 12:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250819122844.483737955@linuxfoundation.org>
2025-08-20 14:36 ` [PATCH 6.16 000/564] 6.16.2-rc2 review Naresh Kamboju
2025-08-22  9:31   ` Dan Carpenter
2025-08-22 12:14     ` Greg Kroah-Hartman [this message]
2025-08-22 12:41       ` Greg Kroah-Hartman

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=2025082242-skyward-mascot-f992@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=achill@achill.org \
    --cc=akpm@linux-foundation.org \
    --cc=anders.roxell@linaro.org \
    --cc=arnd@arndb.de \
    --cc=benjamin.copeland@linaro.org \
    --cc=broonie@kernel.org \
    --cc=conor@kernel.org \
    --cc=dan.carpenter@linaro.org \
    --cc=f.fainelli@gmail.com \
    --cc=hargar@microsoft.com \
    --cc=jack@suse.cz \
    --cc=jiangqi903@gmail.com \
    --cc=jonathanh@nvidia.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=lkft-triage@lists.linaro.org \
    --cc=naresh.kamboju@linaro.org \
    --cc=patches@kernelci.org \
    --cc=patches@lists.linux.dev \
    --cc=pavel@denx.de \
    --cc=rwarsow@gmx.de \
    --cc=shuah@kernel.org \
    --cc=srw@sladewatkins.net \
    --cc=stable@vger.kernel.org \
    --cc=sudipm.mukherjee@gmail.com \
    --cc=torvalds@linux-foundation.org \
    --cc=tytso@mit.edu \
    --cc=yi.zhang@huaweicloud.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;
as well as URLs for NNTP newsgroup(s).