diff options
| author | Carsten Otte <cotte@de.ibm.com> | 2011-10-30 15:17:00 +0100 |
|---|---|---|
| committer | Martin Schwidefsky <schwidefsky@de.ibm.com> | 2011-10-30 15:16:44 +0100 |
| commit | a9162f238a84ee05b09ea4b0ebd97fb20448c28c (patch) | |
| tree | 06364148f57e6833bf7c7e66fa69181e141792ba /arch/microblaze | |
| parent | 69ba97436647f3b793f8e0784d1cde63adf241ea (diff) | |
| download | linux-a9162f238a84ee05b09ea4b0ebd97fb20448c28c.tar.gz | |
[S390] fix possible deadlock in gmap_map_segment
Fix possible deadlock reported by lockdep:
qemu-system-s39/2963 is trying to acquire lock:
(&mm->mmap_sem){++++++}, at: gmap_alloc_table+0x9c/0x120
but task is already holding lock:
(&mm->mmap_sem){++++++}, at: gmap_map_segment+0xa6/0x27c
Actually gmap_alloc_table is the only called in gmap_map_segment with
mmap_sem held, thus it's safe to simply remove the inner lock.
Signed-off-by: Carsten Otte <cotte@de.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
Diffstat (limited to 'arch/microblaze')
0 files changed, 0 insertions, 0 deletions