diff options
| author | Miao Xie <miaox@cn.fujitsu.com> | 2010-02-02 08:46:44 +0000 |
|---|---|---|
| committer | Chris Mason <chris.mason@oracle.com> | 2010-02-04 11:31:44 -0500 |
| commit | d7ce5843bb28ada6845ab2ae8510ba3f12d33154 (patch) | |
| tree | c7468abdcaa1d59d789af027984abfdc1bda5248 /fs/btrfs/disk-io.c | |
| parent | 014e4ac4f7d9c981750491fa40ea35efadc9ed49 (diff) | |
| download | kernel_samsung_smdk4412-d7ce5843bb28ada6845ab2ae8510ba3f12d33154.zip kernel_samsung_smdk4412-d7ce5843bb28ada6845ab2ae8510ba3f12d33154.tar.gz kernel_samsung_smdk4412-d7ce5843bb28ada6845ab2ae8510ba3f12d33154.tar.bz2 | |
Btrfs: remove BUG_ON() due to mounting bad filesystem
Mounting a bad filesystem caused a BUG_ON(). The following is steps to
reproduce it.
# mkfs.btrfs /dev/sda2
# mount /dev/sda2 /mnt
# mkfs.btrfs /dev/sda1 /dev/sda2
(the program says that /dev/sda2 was mounted, and then exits. )
# umount /mnt
# mount /dev/sda1 /mnt
At the third step, mkfs.btrfs exited in the way of make filesystem. So the
initialization of the filesystem didn't finish. So the filesystem was bad, and
it caused BUG_ON() when mounting it. But BUG_ON() should be called by the wrong
code, not user's operation, so I think it is a bug of btrfs.
This patch fixes it.
Signed-off-by: Miao Xie <miaox@cn.fujitsu.com>
Signed-off-by: Chris Mason <chris.mason@oracle.com>
Diffstat (limited to 'fs/btrfs/disk-io.c')
| -rw-r--r-- | fs/btrfs/disk-io.c | 7 |
1 files changed, 6 insertions, 1 deletions
diff --git a/fs/btrfs/disk-io.c b/fs/btrfs/disk-io.c index 87b2554..2b59201 100644 --- a/fs/btrfs/disk-io.c +++ b/fs/btrfs/disk-io.c @@ -1982,7 +1982,12 @@ struct btrfs_root *open_ctree(struct super_block *sb, if (!(sb->s_flags & MS_RDONLY)) { ret = btrfs_recover_relocation(tree_root); - BUG_ON(ret); + if (ret < 0) { + printk(KERN_WARNING + "btrfs: failed to recover relocation\n"); + err = -EINVAL; + goto fail_trans_kthread; + } } location.objectid = BTRFS_FS_TREE_OBJECTID; |