diff options
| author | Linus Torvalds <torvalds@linux-foundation.org> | 2020-03-11 13:35:34 -0700 |
|---|---|---|
| committer | Linus Torvalds <torvalds@linux-foundation.org> | 2020-03-11 13:35:34 -0700 |
| commit | e6e6ec48dd0fa12e8a2d1ff6b55cd907401bd7fe (patch) | |
| tree | 891f03343ce73f6945c9d65a226e79bc59ccb0d0 /include | |
| parent | addcb1d0ee31aa1472a7afd31a63162423af9c93 (diff) | |
| parent | 2b4eae95c7361e0a147b838715c8baa1380a428f (diff) | |
| download | lwn-e6e6ec48dd0fa12e8a2d1ff6b55cd907401bd7fe.tar.gz lwn-e6e6ec48dd0fa12e8a2d1ff6b55cd907401bd7fe.zip | |
Merge tag 'fscrypt-for-linus' of git://git.kernel.org/pub/scm/fs/fscrypt/fscrypt
Pull fscrypt fix from Eric Biggers:
"Fix a bug where if userspace is writing to encrypted files while the
FS_IOC_REMOVE_ENCRYPTION_KEY ioctl (introduced in v5.4) is running,
dirty inodes could be evicted, causing writes could be lost or the
filesystem to hang due to a use-after-free. This was encountered
during real-world use, not just theoretical.
Tested with the existing fscrypt xfstests, and with a new xfstest I
wrote to reproduce this bug. This fix does expose an existing bug with
'-o lazytime' that Ted is working on fixing, but this fix is more
critical and needed anyway regardless of the lazytime fix"
* tag 'fscrypt-for-linus' of git://git.kernel.org/pub/scm/fs/fscrypt/fscrypt:
fscrypt: don't evict dirty inodes after removing key
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions