* [git pull] coredump/exit race fix
@ 2020-11-10 18:28 Al Viro
2020-11-11 13:39 ` pr-tracker-bot
0 siblings, 1 reply; 2+ messages in thread
From: Al Viro @ 2020-11-10 18:28 UTC (permalink / raw)
To: Linus Torvalds; +Cc: linux-kernel
Fix for multithreaded coredump playing fast and loose with getting
registers of secondary threads; if a secondary gets caught in the middle
of exit(2), the conditition it will be stopped in for dumper to examine
might be unusual enough for things to go wrong. Quite a few architectures
are fine with that, but some are not. Sat in -next for a while, survives
local beating, fix is fairly obvious...
The following changes since commit 3650b228f83adda7e5ee532e2b90429c03f7b9ec:
Linux 5.10-rc1 (2020-10-25 15:14:11 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git fixes
for you to fetch changes up to 77f6ab8b7768cf5e6bdd0e72499270a0671506ee:
don't dump the threads that had been already exiting when zapped. (2020-10-28 16:39:49 -0400)
----------------------------------------------------------------
Al Viro (1):
don't dump the threads that had been already exiting when zapped.
kernel/exit.c | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2020-11-11 13:40 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2020-11-10 18:28 [git pull] coredump/exit race fix Al Viro
2020-11-11 13:39 ` pr-tracker-bot
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox