summaryrefslogtreecommitdiff
path: root/crypto/cryptd.c
diff options
context:
space:
mode:
authorDaeho Jeong <daeho.jeong@samsung.com>2016-07-03 21:51:39 (GMT)
committerTheodore Ts'o <tytso@mit.edu>2016-07-03 21:51:39 (GMT)
commitb47820edd1634dc1208f9212b7ecfb4230610a23 (patch)
tree7d02e4756db46ae94ec43fdcd1adfd38156e34a5 /crypto/cryptd.c
parentf70749ca42943faa4d4dcce46dfdcaadb1d0c4b6 (diff)
downloadlinux-b47820edd1634dc1208f9212b7ecfb4230610a23.tar.xz
ext4: avoid modifying checksum fields directly during checksum verification
We temporally change checksum fields in buffers of some types of metadata into '0' for verifying the checksum values. By doing this without locking the buffer, some metadata's checksums, which are being committed or written back to the storage, could be damaged. In our test, several metadata blocks were found with damaged metadata checksum value during recovery process. When we only verify the checksum value, we have to avoid modifying checksum fields directly. Signed-off-by: Daeho Jeong <daeho.jeong@samsung.com> Signed-off-by: Youngjin Gil <youngjin.gil@samsung.com> Signed-off-by: Theodore Ts'o <tytso@mit.edu> Reviewed-by: Darrick J. Wong <darrick.wong@oracle.com>
Diffstat (limited to 'crypto/cryptd.c')
0 files changed, 0 insertions, 0 deletions