linux-kernel - Re: [patch v6 17/20] signal: Queue ignored posixtimers on ignore list

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <871pzsr6rg.ffs@tglx>
Date: Sun, 03 Nov 2024 10:44:35 +0100
From: Thomas Gleixner <tglx@...utronix.de>
To: Frederic Weisbecker <frederic@...nel.org>
Cc: LKML <linux-kernel@...r.kernel.org>, Anna-Maria Behnsen
 <anna-maria@...utronix.de>, John Stultz <jstultz@...gle.com>, Peter
 Zijlstra <peterz@...radead.org>, Ingo Molnar <mingo@...nel.org>, Stephen
 Boyd <sboyd@...nel.org>, Eric Biederman <ebiederm@...ssion.com>, Oleg
 Nesterov <oleg@...hat.com>
Subject: Re: [patch v6 17/20] signal: Queue ignored posixtimers on ignore list

On Sun, Nov 03 2024 at 00:46, Frederic Weisbecker wrote:
> And what about the other callers of flush_sigqueue_mask()? Such as SIGCONT
> removed when SIGSTOP arrives? And the reverse as well? This moves the pending
> timers signals to the ignore list until the signal is unignored, but in that
> case SIGCONT is not ignored? Or perhaps SIGCONT and SIGSTOP can't be set for
> posix timers?

You can set SIGSTOP/CONT on a posix timer. Whether that makes sense or
not is a different question :)

Even on current mainline the behaviour is pretty much unspecified. Some
combinations "work", some not. I just tried out of morbid curiousity. :)

Thanks,

        tglx