On Mon 11-10-10 10:05:34, Eric Sandeen wrote: > Darrick J. Wong wrote: > > 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 code > > already exists in ext4). > > > > Signed-off-by: Darrick J. Wong <djwong@xxxxxxxxxx> > > --- > > Probably worth mentioning the ext4 version is: > > commit 914258bf2cb22bf4336a1b1d90c551b4b11ca5aa > Author: Theodore Ts'o <tytso@xxxxxxx> > Date: Mon Oct 6 21:35:40 2008 -0400 > > ext4/jbd2: Avoid WARN() messages when failing to write to the superblock > > This fixes some very common warnings reported by kerneloops.org > > Signed-off-by: "Theodore Ts'o" <tytso@xxxxxxx> Yup. Done. Thanks. Honza -- Jan Kara <jack@xxxxxxx> SUSE Labs, CR -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
