linux-kernel - [git pull] coredump/exit race fix

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20201110182804.GA705344@ZenIV.linux.org.uk>
Date:   Tue, 10 Nov 2020 18:28:04 +0000
From:   Al Viro <viro@...iv.linux.org.uk>
To:     Linus Torvalds <torvalds@...ux-foundation.org>
Cc:     linux-kernel@...r.kernel.org
Subject: [git pull] coredump/exit race fix

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