linux/fs/jbd
Darrick J. Wong dff6825e9f ext3/jbd: Avoid WARN() messages when failing to write the superblock
This fixes a WARN backtrace in mark_buffer_dirty() that occurs during unmount
when the underlying block device is removed.  This bug has been seen on System
Z when removing all paths from a multipath-backed ext3 mount; on System P when
injecting enough PCI EEH errors to make the SCSI controller go offline; and
similar warnings have been seen (and patched) with ext2/ext4.

The super block update from a previous operation has marked the buffer as in
error, and the flag has to be cleared before doing the update. Similar changes
have been made to ext4 by commit 914258bf2c.

Signed-off-by: Darrick J. Wong <djwong@us.ibm.com>
Signed-off-by: Jan Kara <jack@suse.cz>
2010-10-28 01:30:02 +02:00
..
checkpoint.c remove SWRITE* I/O types 2010-08-18 01:09:01 -04:00
commit.c kill BH_Ordered flag 2010-08-18 01:09:00 -04:00
journal.c ext3/jbd: Avoid WARN() messages when failing to write the superblock 2010-10-28 01:30:02 +02:00
Kconfig Revert "task_struct: make journal_info conditional" 2009-12-17 13:23:24 -08:00
Makefile Linux-2.6.12-rc2 2005-04-16 15:20:36 -07:00
recovery.c jbd: Move debug message into #ifdef area 2010-10-28 01:30:01 +02:00
revoke.c remove SWRITE* I/O types 2010-08-18 01:09:01 -04:00
transaction.c jbd: Use offset_in_page() instead of manual calculation 2010-10-28 01:30:02 +02:00