aboutsummaryrefslogtreecommitdiffstats
path: root/arch/powerpc
diff options
context:
space:
mode:
authorRoland Dreier <roland@purestorage.com>2012-06-07 14:21:13 -0700
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2012-06-17 11:23:10 -0700
commit29684ecb7a675061933fb19531407fa9f9971ab4 (patch)
treeaa0b624b9a3862145503c2163802889f1ccf2eb0 /arch/powerpc
parent3fbec23f6bc97f3721c5345659fbbb71542120c5 (diff)
downloadkernel_samsung_smdk4412-29684ecb7a675061933fb19531407fa9f9971ab4.tar.gz
kernel_samsung_smdk4412-29684ecb7a675061933fb19531407fa9f9971ab4.tar.bz2
kernel_samsung_smdk4412-29684ecb7a675061933fb19531407fa9f9971ab4.zip
btree: fix tree corruption in btree_get_prev()
commit cbf8ae32f66a9ceb8907ad9e16663c2a29e48990 upstream. The memory the parameter __key points to is used as an iterator in btree_get_prev(), so if we save off a bkey() pointer in retry_key and then assign that to __key, we'll end up corrupting the btree internals when we do eg longcpy(__key, bkey(geo, node, i), geo->keylen); to return the key value. What we should do instead is use longcpy() to copy the key value that retry_key points to __key. This can cause a btree to get corrupted by seemingly read-only operations such as btree_for_each_safe. [akpm@linux-foundation.org: avoid the double longcpy()] Signed-off-by: Roland Dreier <roland@purestorage.com> Acked-by: Joern Engel <joern@logfs.org> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'arch/powerpc')
0 files changed, 0 insertions, 0 deletions