Re: [PATCH 6.16 000/564] 6.16.2-rc2 review

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Aug 22, 2025 at 02:14:10PM +0200, Greg Kroah-Hartman wrote:
> 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@xxxxxxxxxxxxxxxxxxx> 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@xxxxxxxxxxxxxxx/
> > 
> > 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.

Now pushed out.




[Index of Archives]     [Reiser Filesystem Development]     [Ceph FS]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Linux FS]     [Yosemite National Park]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Device Mapper]     [Linux Media]

  Powered by Linux