summaryrefslogtreecommitdiff
path: root/fs/crypto/fscrypt_private.h
diff options
context:
space:
mode:
authorEric Biggers <ebiggers@google.com>2023-02-08 09:21:06 +0300
committerEric Biggers <ebiggers@google.com>2023-02-08 09:30:30 +0300
commitec64036e68634231f5891faa2b7a81cdc5dcd001 (patch)
treed96c811a551580f7f9798cb9c1380452160e0921 /fs/crypto/fscrypt_private.h
parent1ad2a626762dca9f3fe6954ce148f9e4fc4c1ba7 (diff)
downloadlinux-ec64036e68634231f5891faa2b7a81cdc5dcd001.tar.xz
fs/super.c: stop calling fscrypt_destroy_keyring() from __put_super()
Now that the key associated with the "test_dummy_operation" mount option is added on-demand when it's needed, rather than immediately when the filesystem is mounted, fscrypt_destroy_keyring() no longer needs to be called from __put_super() to avoid a memory leak on mount failure. Remove this call, which was causing confusion because it appeared to be a sleep-in-atomic bug (though it wasn't, for a somewhat-subtle reason). Signed-off-by: Eric Biggers <ebiggers@google.com> Link: https://lore.kernel.org/r/20230208062107.199831-5-ebiggers@kernel.org
Diffstat (limited to 'fs/crypto/fscrypt_private.h')
0 files changed, 0 insertions, 0 deletions