linux-kernel - [PATCH 0/1] exit: kill signal_struct->quick

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: <20240609142342.GA11165@redhat.com>
Date: Sun, 9 Jun 2024 16:23:42 +0200
From: Oleg Nesterov <oleg@...hat.com>
To: Andrew Morton <akpm@...ux-foundation.org>,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	Tejun Heo <tj@...nel.org>
Cc: linux-kernel@...r.kernel.org
Subject: [PATCH 0/1] exit: kill signal_struct->quick_threads

Hello,

Eric, I can't understand why the commit ("signal: Guarantee that
SIGNAL_GROUP_EXIT is set on process exit") added the new
quick_threads counter. And why, if we forget about --quick_threads,
synchronize_group_exit() has to take siglock unconditionally.
Did I miss something obvious?

Tejun, could you check the note about css_task_iter_advance() in
the changelog? And can't it use thread_group_empty() instead?

Oleg.