Jens Axboe f5f4fc4649 ia64: don't call handle_signal() unless there's actually a signal queued ... 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: b269c229b0 ("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>		2021-03-02 17:22:11 -07:00
..
configs	arch: ia64: Remove CONFIG_OPROFILE support	2021-01-22 12:12:14 +05:30
hp/common	dma-mapping: split <linux/dma-mapping.h>	2020-10-06 07:07:03 +02:00
include	Kbuild updates for v5.12	2021-02-25 10:17:31 -08:00
kernel	ia64: don't call handle_signal() unless there's actually a signal queued	2021-03-02 17:22:11 -07:00
lib	Merge branch 'work.csum_and_copy' of git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs	2020-10-12 16:24:13 -07:00
mm	mm: simplify parater of function memmap_init_zone()	2021-02-24 13:38:31 -08:00
pci	ia64: remove support for machvecs	2019-08-16 14:32:26 -07:00
scripts	kbuild: remove PYTHON variable	2021-02-01 10:37:19 +09:00
uv	ia64: remove support for machvecs	2019-08-16 14:32:26 -07:00
install.sh
Kconfig	arch: ia64: Remove CONFIG_OPROFILE support	2021-01-22 12:12:14 +05:30
Kconfig.debug	ia64: remove support for machvecs	2019-08-16 14:32:26 -07:00
Makefile	ia64: remove redundant READELF from arch/ia64/Makefile	2021-02-28 15:22:02 +09:00