summaryrefslogtreecommitdiff
path: root/crypto
diff options
context:
space:
mode:
authorJoe Thornber <ejt@redhat.com>2014-11-10 15:03:24 (GMT)
committerMike Snitzer <snitzer@redhat.com>2014-11-10 20:23:58 (GMT)
commit9b460d3699324d570a4d4161c3741431887f102f (patch)
tree2349384b5bb988ddb1b9a1bca9b55c99d577dd71 /crypto
parentc822ed967cba38505713d59ed40a114386ef6c01 (diff)
downloadlinux-9b460d3699324d570a4d4161c3741431887f102f.tar.xz
dm btree: fix a recursion depth bug in btree walking code
The walk code was using a 'ro_spine' to hold it's locked btree nodes. But this data structure is designed for the rolling lock scheme, and as such automatically unlocks blocks that are two steps up the call chain. This is not suitable for the simple recursive walk algorithm, which retraces its steps. This code is only used by the persistent array code, which in turn is only used by dm-cache. In order to trigger it you need to have a mapping tree that is more than 2 levels deep; which equates to 8-16 million cache blocks. For instance a 4T ssd with a very small block size of 32k only just triggers this bug. The fix just places the locked blocks on the stack, and stops using the ro_spine altogether. Signed-off-by: Joe Thornber <ejt@redhat.com> Signed-off-by: Mike Snitzer <snitzer@redhat.com> Cc: stable@vger.kernel.org
Diffstat (limited to 'crypto')
0 files changed, 0 insertions, 0 deletions