diff options
| author | Mike Snitzer <snitzer@redhat.com> | 2018-08-08 20:50:58 -0400 |
|---|---|---|
| committer | Mike Snitzer <snitzer@redhat.com> | 2018-08-08 20:50:58 -0400 |
| commit | c9a5e6a968bd328753b694d19b952068c65dc5e7 (patch) | |
| tree | 7827ac389f9c3559b7ccc27b9c5a819a8e616e82 /drivers/md | |
| parent | 3db2776d9fca45305e6c2065905d9a0e7b2c8212 (diff) | |
dm snapshot: remove stale FIXME in snapshot_map()
Commit ae1093be ("dm snapshot: use mutex instead of rw_semaphore")
eliminated the need to worry about read vs write locking. So remove a
FIXME in snapshot_map() that is concerned about selectively taking a
write lock.
Signed-off-by: Mike Snitzer <snitzer@redhat.com>
Diffstat (limited to 'drivers/md')
| -rw-r--r-- | drivers/md/dm-snap.c | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/drivers/md/dm-snap.c b/drivers/md/dm-snap.c index 6f72ac7bbf9a..ae4b33d10924 100644 --- a/drivers/md/dm-snap.c +++ b/drivers/md/dm-snap.c @@ -1707,8 +1707,6 @@ static int snapshot_map(struct dm_target *ti, struct bio *bio) if (!s->valid) return DM_MAPIO_KILL; - /* FIXME: should only take write lock if we need - * to copy an exception */ mutex_lock(&s->lock); if (!s->valid || (unlikely(s->snapshot_overflowed) && |