linux-kernel - Re: [RFC, PATCH] signals: print_fatal_signal: fix the signr "calculation"

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080308203015.GC83@tv-sign.ru>
Date:	Sat, 8 Mar 2008 23:30:15 +0300
From:	Oleg Nesterov <oleg@...sign.ru>
To:	Roland McGrath <roland@...hat.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Arjan van de Ven <arjan@...radead.org>,
	Ingo Molnar <mingo@...e.hu>, linux-kernel@...r.kernel.org
Subject: Re: [RFC, PATCH] signals: print_fatal_signal: fix the signr "calculation"

On 03/08, Roland McGrath wrote:
>
> Hmm.  I see that non-coredump signals that hit the optimized fatal case in
> __group_complete_signal will cause every thread to have a pending SIGKILL.
> So that will be seen first and prevent the print-out.  So that's what you
> intend to change?

Yes,

> I'm not sure print-fatal-signals was really ever intended for non-coredump
> signals.

Great, thanks! Please ignore this patch then. I was afraid something was
missed here.

Oleg.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/