aboutsummaryrefslogtreecommitdiff
path: root/include/linux/debugobjects.h
diff options
context:
space:
mode:
authorVasily Averin <[email protected]>2006-09-27 01:49:33 -0700
committerLinus Torvalds <[email protected]>2006-09-27 08:26:09 -0700
commit7543fc7b3abfee8c6cd6349ebd5e5fde02fac984 (patch)
treec3525ab6440599fcde96bda0cd41db30308dc2b3 /include/linux/debugobjects.h
parent36faadc144477b4929c8fe60b8053f4472eeb3d2 (diff)
[PATCH] ext3: wrong error behavior
SWsoft Virtuozzo/OpenVZ Linux kernel team has discovered that ext3 error behavior was broken in linux kernels since 2.5.x versions by the following patch: 2002/10/31 02:15:26-05:00 [email protected] Default mount options from superblock for ext2/3 filesystems http://linux.bkbits.net:8080/linux-2.6/gnupatch@3dc0d88eKbV9ivV4ptRNM8fBuA3JBQ In case ext3 file system is mounted with errors=continue (EXT3_ERRORS_CONTINUE) errors should be ignored when possible. However at present in case of any error kernel aborts journal and remounts filesystem to read-only. Such behavior was hit number of times and noted to differ from that of 2.4.x kernels. This patch fixes this: - do nothing in case of EXT3_ERRORS_CONTINUE, - set EXT3_MOUNT_ABORT and call journal_abort() in all other cases - panic() should be called after ext3_commit_super() to save sb marked as EXT3_ERROR_FS Signed-off-by: Vasily Averin <[email protected]> Acked-by: Kirill Korotaev <[email protected]> Cc: Theodore Ts'o <[email protected]> Cc: "Stephen C. Tweedie" <[email protected]> Cc: Mingming Cao <[email protected]> Signed-off-by: Andrew Morton <[email protected]> Signed-off-by: Linus Torvalds <[email protected]>
Diffstat (limited to 'include/linux/debugobjects.h')
0 files changed, 0 insertions, 0 deletions