diff options
| author | Mike Snitzer <snitzer@redhat.com> | 2011-01-13 22:53:46 +0300 |
|---|---|---|
| committer | Alasdair G Kergon <agk@redhat.com> | 2011-01-13 22:53:46 +0300 |
| commit | c217649bf2d60ac119afd71d938278cffd55962b (patch) | |
| tree | 5addf2130d59f9fab614d852ac8fe7724ef78c9f /crypto/testmgr.c | |
| parent | 581548db3b3c0f6e25b500329eb02e3c72e7acbe (diff) | |
| download | linux-c217649bf2d60ac119afd71d938278cffd55962b.tar.xz | |
dm: dont take i_mutex to change device size
No longer needlessly hold md->bdev->bd_inode->i_mutex when changing the
size of a DM device. This additional locking is unnecessary because
i_size_write() is already protected by the existing critical section in
dm_swap_table(). DM already has a reference on md->bdev so the
associated bd_inode may be changed without lifetime concerns.
A negative side-effect of having held md->bdev->bd_inode->i_mutex was
that a concurrent DM device resize and flush (via fsync) would deadlock.
Dropping md->bdev->bd_inode->i_mutex eliminates this potential for
deadlock. The following reproducer no longer deadlocks:
https://www.redhat.com/archives/dm-devel/2009-July/msg00284.html
Signed-off-by: Mike Snitzer <snitzer@redhat.com>
Signed-off-by: Mikulas Patocka <mpatocka@redhat.com>
Signed-off-by: Alasdair G Kergon <agk@redhat.com>
Cc: stable@kernel.org
Diffstat (limited to 'crypto/testmgr.c')
0 files changed, 0 insertions, 0 deletions