summaryrefslogtreecommitdiff
path: root/include/linux/workqueue.h
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2026-05-26 13:37:26 -0700
committerLinus Torvalds <torvalds@linux-foundation.org>2026-05-26 13:37:26 -0700
commite909cedf6800ef493063f18a089f3632817a8c2d (patch)
treed1ff437b168fefda1e63465ef8e1b4a14074250d /include/linux/workqueue.h
parentd60ec36cab338dfe2ae40d73e9c8d6c4af70d2b8 (diff)
parentfb6988b83b4cafe8db63999c1ddff1b7c66d2ff5 (diff)
Merge tag 'linux_kselftest-kunit-fixes-7.1-rc6' of git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest
Pull kunit fix from Shuah Khan: "Fix a use-after-free in kunit debugfs when using kunit.filter when the executor frees dynamically allocated resources after running boot-time tests. This resulted in fatal hardware exception due to invalidation of capability flags on the reclaimed memory on some architectures such as CHERI RISC-V that support the feature, and silent memory corruption on others. The fix for this couples the lifetime of the filtered suite memory allocation to the lifetime of the kunit subsystem and its associated VFS nodes. Ownership of the boot-time suite_set is now transferred to a global tracker ('kunit_boot_suites'), and the memory is cleanly released in kunit_exit() during module teardown" * tag 'linux_kselftest-kunit-fixes-7.1-rc6' of git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest: kunit: fix use-after-free in debugfs when using kunit.filter
Diffstat (limited to 'include/linux/workqueue.h')
0 files changed, 0 insertions, 0 deletions