diff options
| author | Chandan Rajendra <chandan@linux.ibm.com> | 2019-08-11 16:29:41 -0400 |
|---|---|---|
| committer | Theodore Ts'o <tytso@mit.edu> | 2019-08-11 16:29:41 -0400 |
| commit | 547b9ad698b434eadca46319cb47e5875b55ef03 (patch) | |
| tree | 5f4021e39b9df5468089a13f7cdd80357025ee14 /fs/ext4/extents_status.h | |
| parent | 991f52306ab8b5d8427f6f953162b5ab92e88e51 (diff) | |
| download | linux-rpi-547b9ad698b434eadca46319cb47e5875b55ef03.tar.gz linux-rpi-547b9ad698b434eadca46319cb47e5875b55ef03.tar.bz2 linux-rpi-547b9ad698b434eadca46319cb47e5875b55ef03.zip | |
jbd2: flush_descriptor(): Do not decrease buffer head's ref count
When executing generic/388 on a ppc64le machine, we notice the following
call trace,
VFS: brelse: Trying to free free buffer
WARNING: CPU: 0 PID: 6637 at /root/repos/linux/fs/buffer.c:1195 __brelse+0x84/0xc0
Call Trace:
__brelse+0x80/0xc0 (unreliable)
invalidate_bh_lru+0x78/0xc0
on_each_cpu_mask+0xa8/0x130
on_each_cpu_cond_mask+0x130/0x170
invalidate_bh_lrus+0x44/0x60
invalidate_bdev+0x38/0x70
ext4_put_super+0x294/0x560
generic_shutdown_super+0xb0/0x170
kill_block_super+0x38/0xb0
deactivate_locked_super+0xa4/0xf0
cleanup_mnt+0x164/0x1d0
task_work_run+0x110/0x160
do_notify_resume+0x414/0x460
ret_from_except_lite+0x70/0x74
The warning happens because flush_descriptor() drops bh reference it
does not own. The bh reference acquired by
jbd2_journal_get_descriptor_buffer() is owned by the log_bufs list and
gets released when this list is processed. The reference for doing IO is
only acquired in write_dirty_buffer() later in flush_descriptor().
Reported-by: Harish Sriram <harish@linux.ibm.com>
Reviewed-by: Jan Kara <jack@suse.cz>
Signed-off-by: Chandan Rajendra <chandan@linux.ibm.com>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Diffstat (limited to 'fs/ext4/extents_status.h')
0 files changed, 0 insertions, 0 deletions