ext4: save the error code which triggered an ext4_error() in the superblock
This allows the cause of an ext4_error() report to be categorized based on whether it was triggered due to an I/O error, or an memory allocation error, or other possible causes. Most errors are caused by a detected file system inconsistency, so the default code stored in the superblock will be EXT4_ERR_EFSCORRUPTED. Link: https://lore.kernel.org/r/20191204032335.7683-1-tytso@mit.edu Signed-off-by:Theodore Ts'o <tytso@mit.edu>
Showing
- fs/ext4/balloc.c 1 addition, 0 deletionsfs/ext4/balloc.c
- fs/ext4/ext4.h 29 additions, 1 deletionfs/ext4/ext4.h
- fs/ext4/ext4_jbd2.c 3 additions, 0 deletionsfs/ext4/ext4_jbd2.c
- fs/ext4/extents.c 1 addition, 0 deletionsfs/ext4/extents.c
- fs/ext4/ialloc.c 2 additions, 0 deletionsfs/ext4/ialloc.c
- fs/ext4/inline.c 2 additions, 0 deletionsfs/ext4/inline.c
- fs/ext4/inode.c 7 additions, 1 deletionfs/ext4/inode.c
- fs/ext4/mballoc.c 4 additions, 0 deletionsfs/ext4/mballoc.c
- fs/ext4/mmp.c 5 additions, 1 deletionfs/ext4/mmp.c
- fs/ext4/namei.c 4 additions, 0 deletionsfs/ext4/namei.c
- fs/ext4/super.c 67 additions, 1 deletionfs/ext4/super.c
- fs/ext4/xattr.c 3 additions, 1 deletionfs/ext4/xattr.c
Please register or sign in to comment