summaryrefslogtreecommitdiffstats
path: root/fs/hpfs/name.c
diff options
context:
space:
mode:
authorJosef Bacik <josef@redhat.com>2009-10-06 10:04:28 -0400
committerChris Mason <chris.mason@oracle.com>2009-10-06 10:04:28 -0400
commit1cdda9b81ac0e6ee986f034fa02f221679e1c11a (patch)
treeae9394e50bc2418e8c3054de12ed44962d6f261a /fs/hpfs/name.c
parent61d92c328c16419fc96dc50dd16f8b8c695409ec (diff)
Btrfs: fix possible softlockup in the allocator
Like the cluster allocating stuff, we can lockup the box with the normal allocation path. This happens when we 1) Start to cache a block group that is severely fragmented, but has a decent amount of free space. 2) Start to commit a transaction 3) Have the commit try and empty out some of the delalloc inodes with extents that are relatively large. The inodes will not be able to make the allocations because they will ask for allocations larger than a contiguous area in the free space cache. So we will wait for more progress to be made on the block group, but since we're in a commit the caching kthread won't make any more progress and it already has enough free space that wait_block_group_cache_progress will just return. So, if we wait and fail to make the allocation the next time around, just loop and go to the next block group. This keeps us from getting stuck in a softlockup. Thanks, Signed-off-by: Josef Bacik <jbacik@redhat.com> Signed-off-by: Chris Mason <chris.mason@oracle.com>
Diffstat (limited to 'fs/hpfs/name.c')
0 files changed, 0 insertions, 0 deletions