summaryrefslogtreecommitdiff
path: root/kernel/workqueue.c
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2026-10-06 04:51:54 +0200
committerLinus Torvalds <torvalds@linux-foundation.org>2026-10-06 04:51:54 +0200
commit2c3418fffa9d037b2038a6db48be63f9e2291806 (patch)
treeb42aa79b8761e46cd7d169be0ea2b1bb7b25ee7c /kernel/workqueue.c
parent67f0943b394d920b6c142aad8c6af94340342ae7 (diff)
parentdd3ea3fcba7c75493760cdbccd35f029597e8d5e (diff)
downloadlinux-next-2c3418fffa9d037b2038a6db48be63f9e2291806.tar.gz
linux-next-2c3418fffa9d037b2038a6db48be63f9e2291806.zip
Merge tag 'keys-v7.3-rc7' of git://git.kernel.org/pub/scm/linux/kernel/git/jarkko/linux-tpmdd
Pull keys fixes from Jarkko Sakkinen: - key_get_persistent() created a new persistent keyring if one did not exist, but failed to set a timeout on it in an error path, preventing GC. Call key_set_timeout() regardless of key_link() result if a persistent keyring was created. - __key_create_or_update() made a copy of keyring->restrict_link before holding keyring->sem, which could cause add_key() to be executed against stale keyring restrictions. Fix it by copying the value only after taking keyring->sem * tag 'keys-v7.3-rc7' of git://git.kernel.org/pub/scm/linux/kernel/git/jarkko/linux-tpmdd: KEYS: Fix add_key() race with keyring restriction keys: finalize persistent keyring timeout after link attempt
Diffstat (limited to 'kernel/workqueue.c')
0 files changed, 0 insertions, 0 deletions