public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@zeniv.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: [git pull] coredump/exit race fix
Date: Tue, 10 Nov 2020 18:28:04 +0000	[thread overview]
Message-ID: <20201110182804.GA705344@ZenIV.linux.org.uk> (raw)

	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(-)

             reply	other threads:[~2020-11-10 18:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-10 18:28 Al Viro [this message]
2020-11-11 13:39 ` [git pull] coredump/exit race fix pr-tracker-bot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20201110182804.GA705344@ZenIV.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox