summaryrefslogtreecommitdiff
path: root/include/asm-powerpc/git@git.tavy.me:linux.git
diff options
context:
space:
mode:
authorBaokun Li <libaokun@linux.alibaba.com>2026-03-23 14:08:36 +0800
committerTheodore Ts'o <tytso@mit.edu>2026-03-27 23:38:01 -0400
commitec0a7500d8eace5b4f305fa0c594dd148f0e8d29 (patch)
tree0d3bd2961d6d1113246a2c8e4ba14ea64fb5430f /include/asm-powerpc/git@git.tavy.me:linux.git
parent0c90eed1b95335eba4f546e6742a8e4503d79349 (diff)
ext4: fix iloc.bh leak in ext4_fc_replay_inode() error paths
During code review, Joseph found that ext4_fc_replay_inode() calls ext4_get_fc_inode_loc() to get the inode location, which holds a reference to iloc.bh that must be released via brelse(). However, several error paths jump to the 'out' label without releasing iloc.bh: - ext4_handle_dirty_metadata() failure - sync_dirty_buffer() failure - ext4_mark_inode_used() failure - ext4_iget() failure Fix this by introducing an 'out_brelse' label placed just before the existing 'out' label to ensure iloc.bh is always released. Additionally, make ext4_fc_replay_inode() propagate errors properly instead of always returning 0. Reported-by: Joseph Qi <joseph.qi@linux.alibaba.com> Fixes: 8016e29f4362 ("ext4: fast commit recovery path") Signed-off-by: Baokun Li <libaokun@linux.alibaba.com> Reviewed-by: Zhang Yi <yi.zhang@huawei.com> Reviewed-by: Jan Kara <jack@suse.cz> Link: https://patch.msgid.link/20260323060836.3452660-1-libaokun@linux.alibaba.com Signed-off-by: Theodore Ts'o <tytso@mit.edu> Cc: stable@kernel.org
Diffstat (limited to 'include/asm-powerpc/git@git.tavy.me:linux.git')
0 files changed, 0 insertions, 0 deletions