diff options
| author | Josef Bacik <jbacik@fusionio.com> | 2013-04-25 15:55:30 -0400 |
|---|---|---|
| committer | Josef Bacik <jbacik@fusionio.com> | 2013-05-06 15:55:20 -0400 |
| commit | b50c6e250ef91313518dbca96663578237ba8d3c (patch) | |
| tree | 419d87afe4386be50be15fe5cc0cb0b367eeb1ed /fs/qnx4 | |
| parent | 3d7b5a2882133a04716903b1f4878a64c6610842 (diff) | |
| download | linux-3.10-b50c6e250ef91313518dbca96663578237ba8d3c.tar.gz linux-3.10-b50c6e250ef91313518dbca96663578237ba8d3c.tar.bz2 linux-3.10-b50c6e250ef91313518dbca96663578237ba8d3c.zip | |
Btrfs: deal with free space cache errors while replaying log
So everybody who got hit by my fsync bug will still continue to hit this
BUG_ON() in the free space cache, which is pretty heavy handed. So I took a
file system that had this bug and fixed up all the BUG_ON()'s and leaks that
popped up when I tried to mount a broken file system like this. With this patch
we just fail to mount instead of panicing. Thanks,
Signed-off-by: Josef Bacik <jbacik@fusionio.com>
Diffstat (limited to 'fs/qnx4')
0 files changed, 0 insertions, 0 deletions