diff options
| author | Eric Sandeen <[email protected]> | 2020-03-18 19:19:38 +0000 |
|---|---|---|
| committer | Theodore Ts'o <[email protected]> | 2020-03-26 14:56:53 +0000 |
| commit | c96e2b8564adfb8ac14469ebc51ddc1bfecb3ae2 (patch) | |
| tree | 74618bae534180249938c17af378f28cd7146244 /tools/perf/util/scripting-engines/trace-event-python.c | |
| parent | ext4: avoid ENOSPC when avoiding to reuse recently deleted inodes (diff) | |
| download | kernel-c96e2b8564adfb8ac14469ebc51ddc1bfecb3ae2.tar.gz kernel-c96e2b8564adfb8ac14469ebc51ddc1bfecb3ae2.zip | |
ext4: do not commit super on read-only bdev
Under some circumstances we may encounter a filesystem error on a
read-only block device, and if we try to save the error info to the
superblock and commit it, we'll wind up with a noisy error and
backtrace, i.e.:
[ 3337.146838] EXT4-fs error (device pmem1p2): ext4_get_journal_inode:4634: comm mount: inode #0: comm mount: iget: illegal inode #
------------[ cut here ]------------
generic_make_request: Trying to write to read-only block-device pmem1p2 (partno 2)
WARNING: CPU: 107 PID: 115347 at block/blk-core.c:788 generic_make_request_checks+0x6b4/0x7d0
...
To avoid this, commit the error info in the superblock only if the
block device is writable.
Reported-by: Ritesh Harjani <[email protected]>
Signed-off-by: Eric Sandeen <[email protected]>
Reviewed-by: Andreas Dilger <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Theodore Ts'o <[email protected]>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions