summaryrefslogtreecommitdiff
path: root/fs/jbd2/Kconfig
diff options
context:
space:
mode:
authorTheodore Ts'o <tytso@mit.edu>2013-12-09 06:12:59 +0400
committerTheodore Ts'o <tytso@mit.edu>2013-12-09 06:12:59 +0400
commitf6c07cad081ba222d63623d913aafba5586c1d2c (patch)
tree246e353b568d1a921c322307da610b5510ebdaf1 /fs/jbd2/Kconfig
parent30fac0f75da24dd5bb43c9e911d2039a984ac815 (diff)
downloadlinux-f6c07cad081ba222d63623d913aafba5586c1d2c.tar.xz
jbd2: don't BUG but return ENOSPC if a handle runs out of space
If a handle runs out of space, we currently stop the kernel with a BUG in jbd2_journal_dirty_metadata(). This makes it hard to figure out what might be going on. So return an error of ENOSPC, so we can let the file system layer figure out what is going on, to make it more likely we can get useful debugging information). This should make it easier to debug problems such as the one which was reported by: https://bugzilla.kernel.org/show_bug.cgi?id=44731 The only two callers of this function are ext4_handle_dirty_metadata() and ocfs2_journal_dirty(). The ocfs2 function will trigger a BUG_ON(), which means there will be no change in behavior. The ext4 function will call ext4_error_inode() which will print the useful debugging information and then handle the situation using ext4's error handling mechanisms (i.e., which might mean halting the kernel or remounting the file system read-only). Also, since both file systems already call WARN_ON(), drop the WARN_ON from jbd2_journal_dirty_metadata() to avoid two stack traces from being displayed. Signed-off-by: "Theodore Ts'o" <tytso@mit.edu> Cc: ocfs2-devel@oss.oracle.com Acked-by: Joel Becker <jlbec@evilplan.org>
Diffstat (limited to 'fs/jbd2/Kconfig')
0 files changed, 0 insertions, 0 deletions