summaryrefslogtreecommitdiff
path: root/include/linux/workqueue_api.h
diff options
context:
space:
mode:
authorChristian Brauner <brauner@kernel.org>2026-11-09 17:51:19 +0100
committerChristian Brauner <brauner@kernel.org>2026-11-11 11:59:12 +0100
commit2ca2e88b106175c1037939de52cb28e4cb545b9e (patch)
tree27d999a7e16de9f5dbb44d749600914f69c0a84a /include/linux/workqueue_api.h
parentd25c14b2d79e4e8292b19041efd1aae4057bf383 (diff)
ext4: don't read the inode block in ext4_sync_inode_metadata()
Without a journal ext4_sync_inode_metadata() looks the inode table block up with __ext4_get_inode_loc_noinmem() which reads it from disk, with readahead of the inode table on top, if it isn't cached. But a block that isn't cached is neither dirty nor under writeback, so there's nothing to write or to wait for. That read is also something we can't afford once inode eviction calls ->sync_inode_metadata() from reclaim. So look the block up with ext4_get_inode_loc_noio() instead and treat -EAGAIN as nothing to do. Note that ext4_get_inode_loc_noio() also returns -EAGAIN for a block that isn't uptodate. Such a block is being read or failed to be read and can't be dirty either. A block whose write failed still counts as uptodate for ext4_buffer_uptodate() so the write error still gets reported. Suggested-by: Jan Kara <jack@suse.cz> Cc: stable@vger.kernel.org # v7.3 Reviewed-by: Jan Kara <jack@suse.cz> Link: https://patch.msgid.link/20261109-work-inode-metadata_writeback-v3-4-91ac6c024018@kernel.org Signed-off-by: Christian Brauner (Amutable) <brauner@kernel.org>
Diffstat (limited to 'include/linux/workqueue_api.h')
0 files changed, 0 insertions, 0 deletions