]> git.ipfire.org Git - thirdparty/kernel/stable.git/commit
ia64: don't call handle_signal() unless there's actually a signal queued
authorJens Axboe <axboe@kernel.dk>
Wed, 3 Mar 2021 00:22:11 +0000 (17:22 -0700)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Wed, 4 Jan 2023 10:39:21 +0000 (11:39 +0100)
commita1240cc413ebb3ec15ee156d3f18f2d5bf1dfe1f
treec5bc46d64d30c9867878934c7efc788c99cacf40
parente1402ba4df2025d66b81a8c215e452b95d1796d8
ia64: don't call handle_signal() unless there's actually a signal queued

[ Upstream commit f5f4fc4649ae542b1a25670b17aaf3cbb6187acc ]

Sergei and John both reported that ia64 failed to boot in 5.11, and it
was related to signals. Turns out the ia64 signal handling is a bit odd,
it doesn't check the return value of get_signal() for whether there's a
signal to deliver or not. With the introduction of TIF_NOTIFY_SIGNAL,
then task_work could trigger it.

Fix it by only calling handle_signal() if we actually have a real signal
to deliver. This brings it in line with all other archs, too.

Fixes: b269c229b0e8 ("ia64: add support for TIF_NOTIFY_SIGNAL")
Reported-by: Sergei Trofimovich <slyich@gmail.com>
Reported-by: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Tested-by: Sergei Trofimovich <slyich@gmail.com>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
arch/ia64/kernel/signal.c