summaryrefslogtreecommitdiffstats
path: root/fs/jbd2
diff options
context:
space:
mode:
authorAneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>2009-01-06 03:34:30 +0100
committerTheodore Ts'o <tytso@mit.edu>2009-01-06 03:34:30 +0100
commit032115fcef837a00336ddf7bda584e89789ea498 (patch)
tree3c36bca32a6590e675146638992ef988a0fbb430 /fs/jbd2
parentext4: remove extraneous newlines from calls to ext4_error() and ext4_warning() (diff)
downloadlinux-032115fcef837a00336ddf7bda584e89789ea498.tar.xz
linux-032115fcef837a00336ddf7bda584e89789ea498.zip
ext4: Don't overwrite allocation_context ac_status
We can call ext4_mb_check_limits even after successfully allocating the requested blocks. In that case, make sure we don't overwrite ac_status if it already has the status AC_STATUS_FOUND. This fixes the lockdep warning: ============================================= [ INFO: possible recursive locking detected ] 2.6.28-rc6-autokern1 #1 --------------------------------------------- fsstress/11948 is trying to acquire lock: (&meta_group_info[i]->alloc_sem){----}, at: [<c04d9a49>] ext4_mb_load_buddy+0x9f/0x278 ..... stack backtrace: ..... [<c04db974>] ext4_mb_regular_allocator+0xbb5/0xd44 ..... but task is already holding lock: (&meta_group_info[i]->alloc_sem){----}, at: [<c04d9a49>] ext4_mb_load_buddy+0x9f/0x278 Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com> Signed-off-by: "Theodore Ts'o" <tytso@mit.edu> Cc: stable@kernel.org
Diffstat (limited to 'fs/jbd2')
0 files changed, 0 insertions, 0 deletions