summaryrefslogtreecommitdiff
path: root/drivers/md/dm-rq.c
diff options
context:
space:
mode:
authorJoe Thornber <ejt@redhat.com>2015-11-19 13:50:32 +0000
committerMike Snitzer <snitzer@redhat.com>2016-11-14 15:17:47 -0500
commit2e8ed71102ff8fe3919dd3a2d73ac4da72686efc (patch)
tree517679ff39a4d5c3901976181cf41c76e55be3fe /drivers/md/dm-rq.c
parenta25f0944ba9b1d8a6813fd6f1a86f1bd59ac25a6 (diff)
dm block manager: make block locking optional
The block manager's locking is useful for catching cycles that may result from certain btree metadata corruption. But in general it serves as a developer tool to catch bugs in code. Unless you're finding that DM thin provisioning is hanging due to infinite loops within the block manager's access to btree nodes you can safely disable this feature. Signed-off-by: Joe Thornber <ejt@redhat.com> Signed-off-by: Arnd Bergmann <arnd@arndb.de> # do/while(0) macro fix Signed-off-by: Mike Snitzer <snitzer@redhat.com>
Diffstat (limited to 'drivers/md/dm-rq.c')
0 files changed, 0 insertions, 0 deletions