6.16.3-rc1 review
Greg Kroah-Hartman
maintainercover 6.16.3-rc1 review
This is the start of the stable review cycle for the 6.16.3 release. There are 9 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 Sun, 24 Aug 2025 12:35:08 +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.3-rc1.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
-------------
Pseudo-Shortlog of commits:
Greg Kroah-Hartman <[email protected]>
Linux 6.16.3-rc1
Zhang Yi <[email protected]>
ext4: replace ext4_writepage_trans_blocks()
Zhang Yi <[email protected]>
ext4: reserved credits for one extent during the folio writeback
Zhang Yi <[email protected]>
ext4: correct the reserved credits for extent conversion
Zhang Yi <[email protected]>
ext4: enhance tracepoints during the folios writeback
Zhang Yi <[email protected]>
ext4: restart handle if credits are insufficient during allocating blocks
Zhang Yi <[email protected]>
ext4: refactor the block allocation process of ext4_page_mkwrite()
Zhang Yi <[email protected]>
ext4: fix stale data if it bail out of the extents mapping loop
Zhang Yi <[email protected]>
ext4: move the calculation of wbc->nr_to_write to mpage_folio_done()
Zhang Yi <[email protected]>
ext4: process folios writeback in bytes
-------------
Diffstat:
Makefile | 4 +- fs/ext4/ext4.h | 2 +- fs/ext4/extents.c | 6 +- fs/ext4/inline.c | 6 +- fs/ext4/inode.c | 323 +++++++++++++++++++++++++++----------------- fs/ext4/move_extent.c | 3 +- fs/ext4/xattr.c | 2 +- include/trace/events/ext4.h | 47 +++++-- 8 files changed, 251 insertions(+), 142 deletions(-)
Greg Kroah-Hartman
maintainerPATCH 1/9 ext4: process folios writeback in bytes
6.16-stable review patch. If anyone has any objections, please let me know.
------------------
From: Zhang Yi <[email protected]>
commit 1bfe6354e0975fe89c3d25e81b6546d205556a4b upstream.
Since ext4 supports large folios, processing writebacks in pages is no longer appropriate, it can be modified to process writebacks in bytes.
--- fs/ext4/inode.c | 70 ++++++++++++++++++++++---------------------- include/trace/events/ext4.h | 13 +++----- 2 files changed, 42 insertions(+), 41 deletions(-)
fs/ext4/inode.c +36 -34
@@ -1668,11 +1668,12 @@ struct mpage_da_data { unsigned int can_map:1; /* Can writepages call map blocks? *//* These are internal state of ext4_do_writepages() */ -pgoff_t first_page;/* The first page to write */ -pgoff_t next_page;/* Current page to examine */ -pgoff_t last_page;/* Last page to examine */ +loff_t start_pos;/* The start pos to write */ +loff_t next_pos;/* Current pos to examine */ +loff_t end_pos;/* Last pos to examine */ +/* -* Extent to map - this can be after first_page because that can be +* Extent to map - this can be after start_pos because that can be * fully mapped. We somewhat abuse m_flags to store whether the extent * is delalloc or unwritten. */
@@ -1692,38 +1693,38 @@ static void mpage_release_unused_pages(sstruct inode *inode = mpd->inode;struct address_space *mapping = inode->i_mapping; -/* This is necessary when next_page == 0. */ -if (mpd->first_page >= mpd->next_page) +/* This is necessary when next_pos == 0. */ +if (mpd->start_pos >= mpd->next_pos)return ; mpd->scanned_until_end =0 ; - index = mpd->first_page; - end = mpd->next_page -1 ;if (invalidate) {ext4_lblk_t start, last; - start = index << (PAGE_SHIFT - inode->i_blkbits); - last = end << (PAGE_SHIFT - inode->i_blkbits); + start =EXT4_B_TO_LBLK (inode, mpd->start_pos); + last = mpd->next_pos >> inode->i_blkbits;/* * avoid racing with extent status tree scans made by * ext4_insert_delayed_block() */ down_write (&EXT4_I (inode)->i_data_sem); -ext4_es_remove_extent (inode, start, last - start +1 ); +ext4_es_remove_extent (inode, start, last - start);up_write (&EXT4_I (inode)->i_data_sem); }folio_batch_init (&fbatch); -while (index <= end) { - nr =filemap_get_folios (mapping, &index, end, &fbatch); + index = mpd->start_pos >>PAGE_SHIFT ; + end = mpd->next_pos >>PAGE_SHIFT ; +while (index < end) { + nr =filemap_get_folios (mapping, &index, end -1 , &fbatch);if (nr ==0 )break ;for (i =0 ; i < nr; i++) {struct folio *folio = fbatch.folios[i]; -if (folio->index < mpd->first_page) +if (folio_pos (folio) < mpd->start_pos)continue ; -if (folio_next_index (folio) -1 > end) +if (folio_next_index (folio) > end)continue ;BUG_ON (!folio_test_locked (folio));BUG_ON (folio_test_writeback (folio));
@@ -2025,7 +2026,7 @@ int ext4_da_get_block_prep(struct inodestatic void mpage_folio_done (struct mpage_da_data *mpd,struct folio *folio) { - mpd->first_page +=folio_nr_pages (folio); + mpd->start_pos +=folio_size (folio);folio_unlock (folio); }
@@ -2035,7 +2036,7 @@ static int mpage_submit_folio(struct mpaloff_t size;int err; -BUG_ON (folio->index != mpd->first_page); +WARN_ON_ONCE (folio_pos (folio) != mpd->start_pos);folio_clear_dirty_for_io (folio);/* * We have to be very careful here! Nothing protects writeback path
@@ -2447,7 +2448,7 @@ update_disksize:* Update on-disk size after IO is submitted. Races with * truncate are avoided by checking i_size under i_data_sem. */ - disksize = ((loff_t )mpd->first_page) <<PAGE_SHIFT ; + disksize = mpd->start_pos;if (disksize >READ_ONCE (EXT4_I (inode)->i_disksize)) {int err2;loff_t i_size;
@@ -2550,8 +2551,8 @@ static int mpage_prepare_extent_to_map(sstruct address_space *mapping = mpd->inode->i_mapping;struct folio_batch fbatch;unsigned int nr_folios; -pgoff_t index = mpd->first_page; -pgoff_t end = mpd->last_page; +pgoff_t index = mpd->start_pos >>PAGE_SHIFT ; +pgoff_t end = mpd->end_pos >>PAGE_SHIFT ;xa_mark_t tag;int i, err =0 ;int blkbits = mpd->inode->i_blkbits;
@@ -2566,7 +2567,7 @@ static int mpage_prepare_extent_to_map(s tag =PAGECACHE_TAG_DIRTY ; mpd->map.m_len =0 ; - mpd->next_page = index; + mpd->next_pos = mpd->start_pos;if (ext4_should_journal_data (mpd->inode)) { handle =ext4_journal_start (mpd->inode,EXT4_HT_WRITE_PAGE , bpp);
@@ -2597,7 +2598,8 @@ static int mpage_prepare_extent_to_map(s goto out;/* If we can't merge this page, we are done. */ -if (mpd->map.m_len >0 && mpd->next_page != folio->index) +if (mpd->map.m_len >0 && + mpd->next_pos !=folio_pos (folio)) goto out;if (handle) {
@@ -2643,8 +2645,8 @@ static int mpage_prepare_extent_to_map(s }if (mpd->map.m_len ==0 ) - mpd->first_page = folio->index; - mpd->next_page =folio_next_index (folio); + mpd->start_pos =folio_pos (folio); + mpd->next_pos =folio_pos (folio) +folio_size (folio);/* * Writeout when we cannot modify metadata is simple. * Just submit the page. For data=journal mode we
@@ -2787,18 +2789,18 @@ static int ext4_do_writepages(struct mpa writeback_index = mapping->writeback_index;if (writeback_index) cycled =0 ; - mpd->first_page = writeback_index; - mpd->last_page =-1 ; + mpd->start_pos = writeback_index <<PAGE_SHIFT ; + mpd->end_pos =LLONG_MAX ; }else { - mpd->first_page = wbc->range_start >>PAGE_SHIFT ; - mpd->last_page = wbc->range_end >>PAGE_SHIFT ; + mpd->start_pos = wbc->range_start; + mpd->end_pos = wbc->range_end; }ext4_io_submit_init (&mpd->io_submit, wbc); retry:if (wbc->sync_mode ==WB_SYNC_ALL || wbc->tagged_writepages) -tag_pages_for_writeback (mapping, mpd->first_page, - mpd->last_page); +tag_pages_for_writeback (mapping, mpd->start_pos >>PAGE_SHIFT , + mpd->end_pos >>PAGE_SHIFT );blk_start_plug (&plug);/*
@@ -2858,7 +2860,7 @@ retry: } mpd->do_map =1 ; -trace_ext4_da_write_pages (inode, mpd->first_page, wbc); +trace_ext4_da_write_pages (inode, mpd->start_pos, wbc); ret =mpage_prepare_extent_to_map (mpd);if (!ret && mpd->map.m_len) ret = mpage_map_and_submit_extent(handle, mpd,
@@ -2915,8 +2917,8 @@ unplug:blk_finish_plug (&plug);if (!ret && !cycled && wbc->nr_to_write >0 ) { cycled =1 ; - mpd->last_page = writeback_index -1 ; - mpd->first_page =0 ; + mpd->end_pos = (writeback_index <<PAGE_SHIFT ) -1 ; + mpd->start_pos =0 ; goto retry; }
@@ -2926,7 +2928,7 @@ unplug:* Set the writeback_index so that range_cyclic * mode will write it back later */ - mapping->writeback_index = mpd->first_page; + mapping->writeback_index = mpd->start_pos >>PAGE_SHIFT ; out_writepages: trace_ext4_writepages_result(inode, wbc, ret,
include/trace/events/ext4.h +6 -7
@@ -483,15 +483,15 @@ TRACE_EVENT(ext4_writepages, ); TRACE_EVENT(ext4_da_write_pages, - TP_PROTO(struct inode *inode, pgoff_t first_page, + TP_PROTO(struct inode *inode, loff_t start_pos, struct writeback_control *wbc), - TP_ARGS(inode, first_page, wbc), + TP_ARGS(inode, start_pos, wbc), TP_STRUCT__entry( __field( dev_t, dev ) __field( ino_t, ino ) - __field( pgoff_t, first_page ) + __field( loff_t, start_pos ) __field( long, nr_to_write ) __field( int, sync_mode ) ),
@@ -499,15 +499,14 @@ TRACE_EVENT(ext4_da_write_pages,TP_fast_assign ( __entry->dev = inode->i_sb->s_dev; __entry->ino = inode->i_ino; - __entry->first_page = first_page; + __entry->start_pos = start_pos; __entry->nr_to_write = wbc->nr_to_write; __entry->sync_mode = wbc->sync_mode; ), -TP_printk ("dev %d,%d ino %lu first_page %lu nr_to_write %ld " -"sync_mode %d" , +TP_printk ("dev %d,%d ino %lu start_pos 0x%llx nr_to_write %ld sync_mode %d" ,MAJOR (__entry->dev),MINOR (__entry->dev), - (unsigned long ) __entry->ino, __entry->first_page, + (unsigned long ) __entry->ino, __entry->start_pos, __entry->nr_to_write, __entry->sync_mode) );
Greg Kroah-Hartman
maintainerPATCH 2/9 ext4: move the calculation of wbc->nr_to_write to mpage_folio_done()
In reply to Greg Kroah-Hartman6.16-stable review patch. If anyone has any objections, please let me know.
------------------
From: Zhang Yi <[email protected]>
commit f922c8c2461b022a2efd9914484901fb358a5b2a upstream.
mpage_folio_done() should be a more appropriate place than mpage_submit_folio() for updating the wbc->nr_to_write after we have submitted a fully mapped folio. Preparing to make mpage_submit_folio() allows to submit partially mapped folio that is still under processing.
--- fs/ext4/inode.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)
fs/ext4/inode.c +1 -2
@@ -2027,6 +2027,7 @@ int ext4_da_get_block_prep(struct inodestatic void mpage_folio_done (struct mpage_da_data *mpd,struct folio *folio) { mpd->start_pos +=folio_size (folio); + mpd->wbc->nr_to_write -=folio_nr_pages (folio);folio_unlock (folio); }
@@ -2057,8 +2058,6 @@ static int mpage_submit_folio(struct mpa !ext4_verity_in_progress(mpd->inode)) len = size & (len -1 ); err =ext4_bio_write_folio (&mpd->io_submit, folio, len); -if (!err) - mpd->wbc->nr_to_write -=folio_nr_pages (folio);return err; }
Greg Kroah-Hartman
maintainerPATCH 3/9 ext4: fix stale data if it bail out of the extents mapping loop
In reply to Greg Kroah-Hartman6.16-stable review patch. If anyone has any objections, please let me know.
------------------
From: Zhang Yi <[email protected]>
commit ded2d726a3041fce8afd88005cbfe15cd4737702 upstream.
During the process of writing back folios, if mpage_map_and_submit_extent() exits the extent mapping loop due to an ENOSPC or ENOMEM error, it may result in stale data or filesystem inconsistency in environments where the block size is smaller than the folio size.
When mapping a discontinuous folio in mpage_map_and_submit_extent(), some buffers may have already be mapped. If we exit the mapping loop prematurely, the folio data within the mapped range will not be written back, and the file's disk size will not be updated. Once the transaction that includes this range of extents is committed, this can lead to stale data or filesystem inconsistency.
Fix this by submitting the current processing partially mapped folio.
--- fs/ext4/inode.c | 51 ++++++++++++++++++++++++++++++++++++++++++++++++++- 1 file changed, 50 insertions(+), 1 deletion(-)
fs/ext4/inode.c +50 -1
@@ -2363,6 +2363,47 @@ static int mpage_map_one_extent(handle_t }/* +* This is used to submit mapped buffers in a single folio that is not fully +* mapped for various reasons, such as insufficient space or journal credits. +*/ +static int mpage_submit_partial_folio (struct mpage_da_data *mpd) +{ +struct inode *inode = mpd->inode; +struct folio *folio; +loff_t pos; +int ret; + + folio =filemap_get_folio (inode->i_mapping, + mpd->start_pos >>PAGE_SHIFT ); +if (IS_ERR (folio)) +return PTR_ERR (folio); +/* +* The mapped position should be within the current processing folio +* but must not be the folio start position. +*/ + pos = ((loff_t )mpd->map.m_lblk) << inode->i_blkbits; +if (WARN_ON_ONCE ((folio_pos (folio) == pos) || + !folio_contains (folio, pos >>PAGE_SHIFT ))) +return -EINVAL ; + + ret =mpage_submit_folio (mpd, folio); +if (ret) + goto out; +/* +* Update start_pos to prevent this folio from being released in +* mpage_release_unused_pages(), it will be reset to the aligned folio +* pos when this folio is written again in the next round. Additionally, +* do not update wbc->nr_to_write here, as it will be updated once the +* entire folio has finished processing. +*/ + mpd->start_pos = pos; +out: +folio_unlock (folio); +folio_put (folio); +return ret; +} + +/* * mpage_map_and_submit_extent - map extent starting at mpd->lblk of length * mpd->len and submit pages underlying it for IO *
@@ -2412,8 +2453,16 @@ static int mpage_map_and_submit_extent(h*/ if ((err == -ENOMEM ) || (err == -ENOSPC &&ext4_count_free_clusters (sb))) { -if (progress) +/* +* We may have already allocated extents for +* some bhs inside the folio, issue the +* corresponding data to prevent stale data. +*/ +if (progress) { +if (mpage_submit_partial_folio (mpd)) + goto invalidate_dirty_pages; goto update_disksize; + }return err; } ext4_msg(sb, KERN_CRIT,
Greg Kroah-Hartman
maintainerPATCH 4/9 ext4: refactor the block allocation process of ext4_page_mkwrite()
In reply to Greg Kroah-Hartman6.16-stable review patch. If anyone has any objections, please let me know.
------------------
From: Zhang Yi <[email protected]>
commit 2bddafea3d0d85ee9ac3cf5ba9a4b2f2d2f50257 upstream.
The block allocation process and error handling in ext4_page_mkwrite() is complex now. Refactor it by introducing a new helper function, ext4_block_page_mkwrite(). It will call ext4_block_write_begin() to allocate blocks instead of directly calling block_page_mkwrite(). Preparing to implement retry logic in a subsequent patch to address situations where the reserved journal credits are insufficient. Additionally, this modification will help prevent potential deadlocks that may occur when waiting for folio writeback while holding the transaction handle.
--- fs/ext4/inode.c | 95 +++++++++++++++++++++++++++++--------------------------- 1 file changed, 50 insertions(+), 45 deletions(-)
fs/ext4/inode.c +50 -45
@@ -6622,6 +6622,53 @@ static int ext4_bh_unmapped(handle_t *hareturn !buffer_mapped (bh); } +static int ext4_block_page_mkwrite (struct inode *inode,struct folio *folio, +get_block_t get_block) +{ +handle_t *handle; +loff_t size; +unsigned long len; +int ret; + + handle =ext4_journal_start (inode,EXT4_HT_WRITE_PAGE , +ext4_writepage_trans_blocks (inode)); +if (IS_ERR (handle)) +return PTR_ERR (handle); + +folio_lock (folio); + size =i_size_read (inode); +/* Page got truncated from under us? */ +if (folio->mapping != inode->i_mapping ||folio_pos (folio) > size) { + ret = -EFAULT ; + goto out_error; + } + + len =folio_size (folio); +if (folio_pos (folio) + len > size) + len = size -folio_pos (folio); + + ret =ext4_block_write_begin (handle, folio,0 , len, get_block); +if (ret) + goto out_error; + +if (!ext4_should_journal_data (inode)) { +block_commit_write (folio,0 , len); +folio_mark_dirty (folio); + }else { + ret =ext4_journal_folio_buffers (handle, folio, len); +if (ret) + goto out_error; + } +ext4_journal_stop (handle); +folio_wait_stable (folio); +return ret; + +out_error: +folio_unlock (folio); +ext4_journal_stop (handle); +return ret; +} +vm_fault_t ext4_page_mkwrite (struct vm_fault *vmf) {struct vm_area_struct *vma = vmf->vma;
@@ -6633,8 +6680,7 @@ vm_fault_t ext4_page_mkwrite(struct vm_fstruct file *file = vma->vm_file;struct inode *inode =file_inode (file);struct address_space *mapping = inode->i_mapping; -handle_t *handle; -get_block_t *get_block; +get_block_t *get_block = ext4_get_block;int retries =0 ;if (unlikely (IS_IMMUTABLE (inode)))
@@ -6702,46 +6748,9 @@ vm_fault_t ext4_page_mkwrite(struct vm_f/* OK, we need to fill the hole... */ if (ext4_should_dioread_nolock (inode)) get_block = ext4_get_block_unwritten; -else - get_block = ext4_get_block; retry_alloc: - handle =ext4_journal_start (inode,EXT4_HT_WRITE_PAGE , -ext4_writepage_trans_blocks (inode)); -if (IS_ERR (handle)) { - ret =VM_FAULT_SIGBUS ; - goto out; - } -/* -* Data journalling can't use block_page_mkwrite() because it -* will set_buffer_dirty() before do_journal_get_write_access() -* thus might hit warning messages for dirty metadata buffers. -*/ -if (!ext4_should_journal_data (inode)) { - err =block_page_mkwrite (vma, vmf, get_block); - }else { -folio_lock (folio); - size =i_size_read (inode); -/* Page got truncated from under us? */ -if (folio->mapping != mapping ||folio_pos (folio) > size) { - ret =VM_FAULT_NOPAGE ; - goto out_error; - } - - len =folio_size (folio); -if (folio_pos (folio) + len > size) - len = size -folio_pos (folio); - - err =ext4_block_write_begin (handle, folio,0 , len, - ext4_get_block); -if (!err) { - ret =VM_FAULT_SIGBUS ; -if (ext4_journal_folio_buffers (handle, folio, len)) - goto out_error; - }else { -folio_unlock (folio); - } - } -ext4_journal_stop (handle); +/* Start journal and allocate blocks */ + err =ext4_block_page_mkwrite (inode, folio, get_block);if (err == -ENOSPC &&ext4_should_retry_alloc (inode->i_sb, &retries)) goto retry_alloc; out_ret:
@@ -6750,8 +6759,4 @@ out:filemap_invalidate_unlock_shared (mapping);sb_end_pagefault (inode->i_sb);return ret; -out_error: -folio_unlock (folio); -ext4_journal_stop (handle); - goto out; }
Greg Kroah-Hartman
maintainerPATCH 5/9 ext4: restart handle if credits are insufficient during allocating blocks
In reply to Greg Kroah-Hartman6.16-stable review patch. If anyone has any objections, please let me know.
------------------
From: Zhang Yi <[email protected]>
commit e2c4c49dee64ca2f42ad2958cbe1805de96b6732 upstream.
After large folios are supported on ext4, writing back a sufficiently large and discontinuous folio may consume a significant number of journal credits, placing considerable strain on the journal. For example, in a 20GB filesystem with 1K block size and 1MB journal size, writing back a 2MB folio could require thousands of credits in the worst-case scenario (when each block is discontinuous and distributed across different block groups), potentially exceeding the journal size. This issue can also occur in ext4_write_begin() and ext4_page_mkwrite() when delalloc is not enabled.
Fix this by ensuring that there are sufficient journal credits before allocating an extent in mpage_map_one_extent() and ext4_block_write_begin(). If there are not enough credits, return -EAGAIN, exit the current mapping loop, restart a new handle and a new transaction, and allocating blocks on this folio again in the next iteration.
--- fs/ext4/inode.c | 41 ++++++++++++++++++++++++++++++++++++----- 1 file changed, 36 insertions(+), 5 deletions(-)
fs/ext4/inode.c +36 -5
@@ -877,6 +877,26 @@ static void ext4_update_bh_state(struct }while (unlikely (!try_cmpxchg (&bh->b_state, &old_state, new_state))); } +/* +* Make sure that the current journal transaction has enough credits to map +* one extent. Return -EAGAIN if it cannot extend the current running +* transaction. +*/ +static inline int ext4_journal_ensure_extent_credits (handle_t *handle, +struct inode *inode) +{ +int credits; +int ret; + +/* Called from ext4_da_write_begin() which has no handle started? */ +if (!handle) +return 0 ; + + credits =ext4_chunk_trans_blocks (inode,1 ); + ret =__ext4_journal_ensure_credits (handle, credits, credits,0 ); +return ret <=0 ? ret : -EAGAIN ; +} +static int _ext4_get_block (struct inode *inode,sector_t iblock,struct buffer_head *bh,int flags) {
@@ -1175,7 +1195,9 @@ int ext4_block_write_begin(handle_t *hanclear_buffer_new (bh);if (!buffer_mapped (bh)) {WARN_ON (bh->b_size != blocksize); - err =get_block (inode, block, bh,1 ); + err =ext4_journal_ensure_extent_credits (handle, inode); +if (!err) + err =get_block (inode, block, bh,1 );if (err)break ;if (buffer_new (bh)) {
@@ -1374,8 +1396,9 @@ retry_journal:ext4_orphan_del (NULL , inode); } -if (ret == -ENOSPC && -ext4_should_retry_alloc (inode->i_sb, &retries)) +if (ret == -EAGAIN || + (ret == -ENOSPC && +ext4_should_retry_alloc (inode->i_sb, &retries))) goto retry_journal;folio_put (folio);return ret;
@@ -2324,6 +2347,11 @@ static int mpage_map_one_extent(handle_tint get_blocks_flags;int err, dioread_nolock; +/* Make sure transaction has enough credits for this extent */ + err =ext4_journal_ensure_extent_credits (handle, inode); +if (err <0 ) +return err; +trace_ext4_da_write_pages_extent (inode, map);/* * Call ext4_map_blocks() to allocate any delayed allocation blocks, or
@@ -2451,7 +2479,7 @@ static int mpage_map_and_submit_extent(h* In the case of ENOSPC, if ext4_count_free_blocks() * is non-zero, a commit should free up blocks. */ -if ((err == -ENOMEM ) || +if ((err == -ENOMEM ) || (err == -EAGAIN ) || (err == -ENOSPC &&ext4_count_free_clusters (sb))) {/* * We may have already allocated extents for
@@ -2957,6 +2985,8 @@ retry: ret =0 ;continue ; } +if (ret == -EAGAIN ) + ret =0 ;/* Fatal error - ENOMEM, EIO... */ if (ret)break ;
@@ -6751,7 +6781,8 @@ vm_fault_t ext4_page_mkwrite(struct vm_f retry_alloc:/* Start journal and allocate blocks */ err =ext4_block_page_mkwrite (inode, folio, get_block); -if (err == -ENOSPC &&ext4_should_retry_alloc (inode->i_sb, &retries)) +if (err == -EAGAIN || + (err == -ENOSPC &&ext4_should_retry_alloc (inode->i_sb, &retries))) goto retry_alloc; out_ret: ret =vmf_fs_error (err);
Greg Kroah-Hartman
maintainerPATCH 6/9 ext4: enhance tracepoints during the folios writeback
In reply to Greg Kroah-Hartman6.16-stable review patch. If anyone has any objections, please let me know.
------------------
From: Zhang Yi <[email protected]>
commit 6b132759b0fe78e518abafb62190c294100db6d6 upstream.
After mpage_map_and_submit_extent() supports restarting handle if credits are insufficient during allocating blocks, it is more likely to exit the current mapping iteration and continue to process the current processing partially mapped folio again. The existing tracepoints are not sufficient to track this situation, so enhance the tracepoints to track the writeback position and the return value before and after submitting the folios.
--- fs/ext4/inode.c | 5 ++++- include/trace/events/ext4.h | 42 +++++++++++++++++++++++++++++++++++++----- 2 files changed, 41 insertions(+), 6 deletions(-)
fs/ext4/inode.c +4 -1
@@ -2936,7 +2936,8 @@ retry: } mpd->do_map =1 ; -trace_ext4_da_write_pages (inode, mpd->start_pos, wbc); +trace_ext4_da_write_folios_start (inode, mpd->start_pos, + mpd->next_pos, wbc); ret =mpage_prepare_extent_to_map (mpd);if (!ret && mpd->map.m_len) ret = mpage_map_and_submit_extent(handle, mpd,
@@ -2974,6 +2975,8 @@ retry: }else ext4_put_io_end (mpd->io_submit.io_end); mpd->io_submit.io_end =NULL ; +trace_ext4_da_write_folios_end (inode, mpd->start_pos, + mpd->next_pos, wbc, ret);if (ret == -ENOSPC && sbi->s_journal) {/*
include/trace/events/ext4.h +37 -5
69 lines not on this page · raw message
Greg Kroah-Hartman
maintainerPATCH 7/9 ext4: correct the reserved credits for extent conversion
In reply to Greg Kroah-Hartman6.16-stable review patch. If anyone has any objections, please let me know.
------------------
From: Zhang Yi <[email protected]>
commit 95ad8ee45cdbc321c135a2db895d48b374ef0f87 upstream.
Now, we reserve journal credits for converting extents in only one page to written state when the I/O operation is complete. This is insufficient when large folio is enabled.
Fix this by reserving credits for converting up to one extent per block in the largest 2MB folio, this calculation should only involve extents index and leaf blocks, so it should not estimate too many credits.
--- fs/ext4/inode.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
fs/ext4/inode.c +3 -3
@@ -2850,12 +2850,12 @@ static int ext4_do_writepages(struct mpa mpd->journalled_more_data =0 ;if (ext4_should_dioread_nolock (inode)) { +int bpf =ext4_journal_blocks_per_folio (inode);/* * We may need to convert up to one extent per block in -* the page and we may dirty the inode. +* the folio and we may dirty the inode. */ - rsv_blocks =1 +ext4_chunk_trans_blocks (inode, -PAGE_SIZE >> inode->i_blkbits); + rsv_blocks =1 +ext4_ext_index_trans_blocks (inode, bpf); }if (wbc->range_start ==0 && wbc->range_end ==LLONG_MAX )
Greg Kroah-Hartman
maintainerPATCH 8/9 ext4: reserved credits for one extent during the folio writeback
In reply to Greg Kroah-Hartman6.16-stable review patch. If anyone has any objections, please let me know.
------------------
From: Zhang Yi <[email protected]>
commit bbbf150f3f85619569ac19dc6458cca7c492e715 upstream.
After ext4 supports large folios, reserving journal credits for one maximum-ordered folio based on the worst case cenario during the writeback process can easily exceed the maximum transaction credits. Additionally, reserving journal credits for one page is also no longer appropriate.
Currently, the folio writeback process can either extend the journal credits or initiate a new transaction if the currently reserved journal credits are insufficient. Therefore, it can be modified to reserve credits for only one extent at the outset. In most cases involving continuous mapping, these credits are generally adequate, and we may only need to perform some basic credit expansion. However, in extreme cases where the block size and folio size differ significantly, or when the folios are sufficiently discontinuous, it may be necessary to restart a new transaction and resubmit the folios.
--- fs/ext4/inode.c | 25 ++++++++----------------- 1 file changed, 8 insertions(+), 17 deletions(-)
fs/ext4/inode.c +8 -17
@@ -2548,21 +2548,6 @@ update_disksize:return err; } -/* -* Calculate the total number of credits to reserve for one writepages -* iteration. This is called from ext4_writepages(). We map an extent of -* up to MAX_WRITEPAGES_EXTENT_LEN blocks and then we go on and finish mapping -* the last partial page. So in total we can map MAX_WRITEPAGES_EXTENT_LEN + -* bpp - 1 blocks in bpp different extents. -*/ -static int ext4_da_writepages_trans_blocks (struct inode *inode) -{ -int bpp =ext4_journal_blocks_per_folio (inode); - -return ext4_meta_trans_blocks (inode, -MAX_WRITEPAGES_EXTENT_LEN + bpp -1 , bpp); -} -static int ext4_journal_folio_buffers (handle_t *handle,struct folio *folio,size_t len) {
@@ -2919,8 +2904,14 @@ retry:* not supported by delalloc. */ BUG_ON (ext4_should_journal_data (inode)); - needed_blocks =ext4_da_writepages_trans_blocks (inode); - +/* +* Calculate the number of credits needed to reserve for one +* extent of up to MAX_WRITEPAGES_EXTENT_LEN blocks. It will +* attempt to extend the transaction or start a new iteration +* if the reserved credits are insufficient. +*/ + needed_blocks =ext4_chunk_trans_blocks (inode, +MAX_WRITEPAGES_EXTENT_LEN );/* start a new transaction */ handle =ext4_journal_start_with_reserve (inode,EXT4_HT_WRITE_PAGE , needed_blocks, rsv_blocks);
Greg Kroah-Hartman
maintainerPATCH 9/9 ext4: replace ext4_writepage_trans_blocks()
In reply to Greg Kroah-Hartman6.16-stable review patch. If anyone has any objections, please let me know.
------------------
From: Zhang Yi <[email protected]>
commit 57661f28756c59510e31543520b5b8f5e591f384 upstream.
After ext4 supports large folios, the semantics of reserving credits in pages is no longer applicable. In most scenarios, reserving credits in extents is sufficient. Therefore, introduce ext4_chunk_trans_extent() to replace ext4_writepage_trans_blocks(). move_extent_per_page() is the only remaining location where we are still processing extents in pages.
--- fs/ext4/ext4.h | 2 +- fs/ext4/extents.c | 6 +++--- fs/ext4/inline.c | 6 +++--- fs/ext4/inode.c | 33 +++++++++++++++------------------ fs/ext4/move_extent.c | 3 ++- fs/ext4/xattr.c | 2 +- 6 files changed, 25 insertions(+), 27 deletions(-)
fs/ext4/ext4.h +1 -1
@@ -3064,9 +3064,9 @@ extern int ext4_punch_hole(struct file *extern void ext4_set_inode_flags (struct inode *,bool init);extern int ext4_alloc_da_blocks (struct inode *inode);extern void ext4_set_aops (struct inode *inode); -extern int ext4_writepage_trans_blocks (struct inode *);extern int ext4_normal_submit_inode_data_buffers (struct jbd2_inode *jinode);extern int ext4_chunk_trans_blocks (struct inode *,int nrblocks); +extern int ext4_chunk_trans_extent (struct inode *inode,int nrblocks);extern int ext4_meta_trans_blocks (struct inode *inode,int lblocks,int pextents); extern int ext4_zero_partial_blocks(handle_t *handle, struct inode *inode,
fs/ext4/extents.c +3 -3
@@ -5171,7 +5171,7 @@ ext4_ext_shift_path_extents(struct ext4_ credits = depth +2 ; } - restart_credits =ext4_writepage_trans_blocks (inode); + restart_credits =ext4_chunk_trans_extent (inode,0 ); err =ext4_datasem_ensure_credits (handle, inode, credits, restart_credits,0 );if (err) {
@@ -5431,7 +5431,7 @@ static int ext4_collapse_range(struct fitruncate_pagecache (inode, start); - credits =ext4_writepage_trans_blocks (inode); + credits =ext4_chunk_trans_extent (inode,0 ); handle =ext4_journal_start (inode,EXT4_HT_TRUNCATE , credits);if (IS_ERR (handle))return PTR_ERR (handle);
@@ -5527,7 +5527,7 @@ static int ext4_insert_range(struct filetruncate_pagecache (inode, start); - credits =ext4_writepage_trans_blocks (inode); + credits =ext4_chunk_trans_extent (inode,0 ); handle =ext4_journal_start (inode,EXT4_HT_TRUNCATE , credits);if (IS_ERR (handle))return PTR_ERR (handle);
fs/ext4/inline.c +3 -3
@@ -570,7 +570,7 @@ static int ext4_convert_inline_data_to_ereturn 0 ; } - needed_blocks =ext4_writepage_trans_blocks (inode); + needed_blocks =ext4_chunk_trans_extent (inode,1 ); ret =ext4_get_inode_loc (inode, &iloc);if (ret)
@@ -1874,7 +1874,7 @@ int ext4_inline_data_truncate(struct ino }; - needed_blocks =ext4_writepage_trans_blocks (inode); + needed_blocks =ext4_chunk_trans_extent (inode,1 ); handle =ext4_journal_start (inode,EXT4_HT_INODE , needed_blocks);if (IS_ERR (handle))return PTR_ERR (handle);
@@ -1994,7 +1994,7 @@ int ext4_convert_inline_data(struct inodreturn 0 ; } - needed_blocks =ext4_writepage_trans_blocks (inode); + needed_blocks =ext4_chunk_trans_extent (inode,1 ); iloc.bh =NULL ; error =ext4_get_inode_loc (inode, &iloc);
fs/ext4/inode.c +15 -18
@@ -1296,7 +1296,8 @@ static int ext4_write_begin(struct file* Reserve one block more for addition to orphan list in case * we allocate blocks but write fails for some reason */ - needed_blocks =ext4_writepage_trans_blocks (inode) +1 ; + needed_blocks =ext4_chunk_trans_extent (inode, +ext4_journal_blocks_per_folio (inode)) +1 ; index = pos >>PAGE_SHIFT ;if (ext4_test_inode_state (inode,EXT4_STATE_MAY_INLINE_DATA )) {
@@ -4464,7 +4465,7 @@ int ext4_punch_hole(struct file *file, lreturn ret;if (ext4_test_inode_flag (inode,EXT4_INODE_EXTENTS )) - credits =ext4_writepage_trans_blocks (inode); + credits =ext4_chunk_trans_extent (inode,2 );else credits =ext4_blocks_for_truncate (inode); handle =ext4_journal_start (inode,EXT4_HT_TRUNCATE , credits);
@@ -4613,7 +4614,7 @@ int ext4_truncate(struct inode *inode) }if (ext4_test_inode_flag (inode,EXT4_INODE_EXTENTS )) - credits =ext4_writepage_trans_blocks (inode); + credits =ext4_chunk_trans_extent (inode,1 );else credits =ext4_blocks_for_truncate (inode);
@@ -6256,25 +6257,19 @@ int ext4_meta_trans_blocks(struct inode }/* -* Calculate the total number of credits to reserve to fit -* the modification of a single pages into a single transaction, -* which may include multiple chunks of block allocations. -* -* This could be called via ext4_write_begin() -* -* We need to consider the worse case, when -* one new block per extent. +* Calculate the journal credits for modifying the number of blocks +* in a single extent within one transaction. 'nrblocks' is used only +* for non-extent inodes. For extent type inodes, 'nrblocks' can be +* zero if the exact number of blocks is unknown. */ -int ext4_writepage_trans_blocks (struct inode *inode) +int ext4_chunk_trans_extent (struct inode *inode,int nrblocks) { -int bpp =ext4_journal_blocks_per_folio (inode);int ret; - ret =ext4_meta_trans_blocks (inode, bpp, bpp); - + ret =ext4_meta_trans_blocks (inode, nrblocks,1 );/* Account for data blocks for journalled mode */ if (ext4_should_journal_data (inode)) - ret += bpp; + ret += nrblocks;return ret; }
@@ -6652,10 +6647,12 @@ static int ext4_block_page_mkwrite(struchandle_t *handle;loff_t size;unsigned long len; +int credits;int ret; - handle =ext4_journal_start (inode,EXT4_HT_WRITE_PAGE , -ext4_writepage_trans_blocks (inode)); + credits =ext4_chunk_trans_extent (inode, +ext4_journal_blocks_per_folio (inode)); + handle =ext4_journal_start (inode,EXT4_HT_WRITE_PAGE , credits);if (IS_ERR (handle))return PTR_ERR (handle);
fs/ext4/move_extent.c +2 -1
@@ -280,7 +280,8 @@ move_extent_per_page(struct file *o_filp*/ again: *err =0 ; - jblocks =ext4_writepage_trans_blocks (orig_inode) *2 ; + jblocks =ext4_meta_trans_blocks (orig_inode, block_len_in_page, + block_len_in_page) *2 ; handle =ext4_journal_start (orig_inode,EXT4_HT_MOVE_EXTENTS , jblocks);if (IS_ERR (handle)) { *err =PTR_ERR (handle);
fs/ext4/xattr.c +1 -1
@@ -962,7 +962,7 @@ int __ext4_xattr_set_credits(struct supe* so we need to reserve credits for this eventuality */ if (inode &&ext4_has_inline_data (inode)) - credits +=ext4_writepage_trans_blocks (inode) +1 ; + credits +=ext4_chunk_trans_extent (inode,1 ) +1 ;/* We are done if ea_inode feature is not enabled. */ if (!ext4_has_feature_ea_inode (sb))
Hi
no regressions here on x86_64 (RKL, Intel 11th Gen. CPU)
Thanks
Quoted 4 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 6.16.3 release. There are 9 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.
Hi Greg
6.16.3-rc1 compiles on x86_64 (Xeon E5-1620 v2, Slackware64-15.0), and boots & runs on x86_64 (AMD Ryzen 5 7520U, Slackware64-current).
No regressions observed, apart from the one already mentioned for 6.16.2-rc1.
Thus I tested 6.16.3-rc1 with V3 of the patch and it seems to work ok:
https://lore.kernel.org/stable/[email protected]/
Quoted 9 lines · Markus Reichelt
Quoted 4 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 6.16.3 release. There are 9 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.
Hi Greg
Quoted 7 lines
6.16.3-rc1 compiles on
x86_64(Xeon E5-1620 v2, Slackware64-15.0), and boots & runs onx86_64(AMD Ryzen 5 7520U, Slackware64-current).No regressions observed, apart from the one already mentioned for 6.16.2-rc1.
Thus I tested 6.16.3-rc1 with V3 of the patch and it seems to work ok:
https://lore.kernel.org/stable/[email protected]/
Yeah, that one needs to get into Linus's tree, hopefully soon...
Hi Greg
Quoted 10 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 6.16.3 release. There are 9 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 Sun, 24 Aug 2025 12:35:08 +0000. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
Quoted 9 lines
https://www.kernel.org/pub/linux/kernel/v6.x/stable-review/patch-6.16.3-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-6.16.y
and the diffstat can be found below.thanks,
greg k-h
6.16.3-rc1 tested.
Build successfully completed.
Boot successfully completed.
No dmesg regressions.
Video output normal.
Sound output normal.
Lenovo ThinkPad X1 Carbon Gen10(Intel i7-1260P(x86_64) arch linux)
[ 0.000000] Linux version 6.16.3-rc1rv-g3fb8628191b4
(takeshi@ThinkPadX1Gen10J0764) (gcc (GCC) 15.2.1 20250813, GNU ld (GNU Binutils) 2.45.0) #1 SMP PREEMPT_DYNAMIC Fri Aug 22 23:37:39 JST 2025
Thanks
Quoted 9 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 6.16.3 release. There are 9 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 Sun, 24 Aug 2025 12:35:08 +0000. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
Quoted 8 lines
https://www.kernel.org/pub/linux/kernel/v6.x/stable-review/patch-6.16.3-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-6.16.y
and the diffstat can be found below.thanks,
greg k-h
On ARCH_BRCMSTB using 32-bit and 64-bit ARM kernels, build tested on BMIPS_GENERIC:
Signature · 1 line
Florian
Am 22.08.2025 um 14:37 schrieb Greg Kroah-Hartman:
Quoted 4 lines
This is the start of the stable review cycle for the 6.16.3 release. There are 9 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.
Builds, boots and works on my 2-socket Ivy Bridge Xeon E5-2697 v2 server. No dmesg oddities or regressions found.
Beste Grüße,
Peter Schneider
Signature · 8 lines
Climb the mountain not to plant your flag, but to embrace the challenge, enjoy the air and behold the view. Climb it so you can see the world, not so the world can see you. -- David McCullough Jr. OpenPGP: 0xA3828BD796CCE11A8CADE8866E3A92C92C3FF244 Download: https://www.peters-netzplatz.de/download/pschneider1968_pub.asc https://keys.mailvelope.com/pks/lookup?op=get&[email protected] https://keys.mailvelope.com/pks/lookup?op=get&[email protected]
Quoted 10 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 6.16.3 release. There are 9 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 Sun, 24 Aug 2025 12:35:08 +0000. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
Quoted 8 lines
https://www.kernel.org/pub/linux/kernel/v6.x/stable-review/patch-6.16.3-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-6.16.y
and the diffstat can be found below.thanks,
greg k-h
Results from Linaro’s test farm.
No regressions on arm64, arm, x86_64, and i386.
NOTE:
The reported warning has been resolved in this review cycle.
WARNING: fs/jbd2/transaction.c:334 at start_this_handle
## Build
* kernel: 6.16.3-rc1
* git: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
* git commit: 3fb8628191b4a7d912baf880840804056f3f44ad
* git describe: v6.16.2-10-g3fb8628191b4
* test details:
https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-6.16.y/build/v6.16.2-10-g3fb8628191b4
## Test Regressions (compared to v6.16-1186-gb81166f7d590)
## Metric Regressions (compared to v6.16-1186-gb81166f7d590)
## Test Fixes (compared to v6.16-1186-gb81166f7d590)
## Metric Fixes (compared to v6.16-1186-gb81166f7d590)
## Test result summary
total: 348595, pass: 321612, fail: 6867, skip: 20116, xfail: 0
## Build Summary
* arc: 5 total, 5 passed, 0 failed
* arm: 139 total, 138 passed, 1 failed
* arm64: 57 total, 56 passed, 1 failed
* i386: 18 total, 18 passed, 0 failed
* mips: 34 total, 27 passed, 7 failed
* parisc: 4 total, 4 passed, 0 failed
* powerpc: 40 total, 39 passed, 1 failed
* riscv: 25 total, 24 passed, 1 failed
* s390: 22 total, 22 passed, 0 failed
* sh: 5 total, 5 passed, 0 failed
* sparc: 4 total, 3 passed, 1 failed
* x86_64: 49 total, 48 passed, 1 failed
## Test suites summary
* boot
* commands
* kselftest-arm64
* kselftest-breakpoints
* kselftest-capabilities
* kselftest-cgroup
* kselftest-clone3
* kselftest-core
* kselftest-cpu-hotplug
* kselftest-cpufreq
* kselftest-efivarfs
* kselftest-exec
* kselftest-fpu
* kselftest-ftrace
* kselftest-futex
* kselftest-gpio
* kselftest-intel_pstate
* kselftest-ipc
* kselftest-kcmp
* kselftest-kvm
* kselftest-livepatch
* kselftest-membarrier
* kselftest-memfd
* kselftest-mincore
* kselftest-mm
* kselftest-mqueue
* kselftest-net
* kselftest-net-mptcp
* kselftest-openat2
* kselftest-ptrace
* kselftest-rseq
* kselftest-rtc
* kselftest-rust
* kselftest-seccomp
* kselftest-sigaltstack
* kselftest-size
* kselftest-tc-testing
* kselftest-timers
* kselftest-tmpfs
* kselftest-tpm2
* kselftest-user_events
* kselftest-vDSO
* kselftest-x86
* kunit
* kvm-unit-tests
* lava
* libgpiod
* libhugetlbfs
* log-parser-boot
* log-parser-build-clang
* log-parser-build-gcc
* log-parser-test
* ltp-capability
* ltp-commands
* ltp-containers
* ltp-controllers
* ltp-cpuhotplug
* ltp-crypto
* ltp-cve
* ltp-dio
* ltp-fcntl-locktests
* ltp-fs
* ltp-fs_bind
* ltp-fs_perms_simple
* ltp-hugetlb
* ltp-math
* ltp-mm
* ltp-nptl
* ltp-pty
* ltp-sched
* ltp-smoke
* ltp-syscalls
* ltp-tracing
* modules
* perf
* rcutorture
* rt-tests-cyclicdeadline
* rt-tests-pi-stress
* rt-tests-pmqtest
* rt-tests-rt-migrate-test
* rt-tests-signaltest
--
Linaro LKFT
https://lkft.linaro.org
UDP broadcast is broken in this kernel - the destination ethernet address field is mangled. See:
https://lore.kernel.org/regressions/[email protected]/
As this is bug-for-bug compatible with mainline, I believe stable policy is to wait until this is fixed there before backporting a fix.
All other Librecast network tests passing.
# Librecast Test Results
010/010 [ OK ] libmld
120/120 [ OK ] liblibrecast
CPU/kernel: Linux auntie 6.16.3-rc1-g3fb8628191b4 #47 SMP PREEMPT_DYNAMIC Sat Aug 23 12:39:17 -00 2025 x86_64 AMD Ryzen 9 9950X 16-Core Processor AuthenticAMD GNU/Linux