A-Team_Digital_Solutions/android_kernel_motorola_sm6375
Watch
2
0
Fork
You've already forked android_kernel_motorola_sm6375
 0
mirror of https://github.com/BobTheBlinker/android_kernel_motorola_sm6375.git synced 2026-11-08 11:45:53 -05:00
Code Issues Projects Releases Packages Wiki Activity
android_kernel_motorola_sm6375/fs/crypto
History
Repository files (latest commit first)
Filename Latest commit message Latest commit date
Eric Biggers 0f0909e242 fscrypto: don't use on-stack buffer for key derivation 
With the new (in 4.9) option to use a virtually-mapped stack
(CONFIG_VMAP_STACK), stack buffers cannot be used as input/output for
the scatterlist crypto API because they may not be directly mappable to
struct page.  get_crypt_info() was using a stack buffer to hold the
output from the encryption operation used to derive the per-file key.
Fix it by using a heap buffer.

This bug could most easily be observed in a CONFIG_DEBUG_SG kernel
because this allowed the BUG in sg_set_buf() to be triggered.

Cc: [email protected]
Signed-off-by: Eric Biggers <[email protected]>
Signed-off-by: Theodore Ts'o <[email protected]>
2016-11-19 20:56:13 -05:00
..
crypto.c fscrypto: make XTS tweak initialization endian-independent 2016-10-12 23:30:16 -04:00
fname.c fscrypto: don't use on-stack buffer for filename encryption 2016-11-19 20:56:06 -05:00
Kconfig
keyinfo.c fscrypto: don't use on-stack buffer for key derivation 2016-11-19 20:56:13 -05:00
Makefile
policy.c fscrypto: lock inode while setting encryption policy 2016-10-15 09:48:50 -04:00