--- /dev/null
+From d3dc04cd81e0eaf50b2d09ab051a13300e587439 Mon Sep 17 00:00:00 2001
+From: Jens Axboe <axboe@kernel.dk>
+Date: Thu, 25 Mar 2021 18:22:11 -0600
+Subject: Revert "kernel: freezer should treat PF_IO_WORKER like PF_KTHREAD for freezing"
+
+From: Jens Axboe <axboe@kernel.dk>
+
+commit d3dc04cd81e0eaf50b2d09ab051a13300e587439 upstream.
+
+This reverts commit 15b2219facadec583c24523eed40fa45865f859f.
+
+Before IO threads accepted signals, the freezer using take signals to wake
+up an IO thread would cause them to loop without any way to clear the
+pending signal. That is no longer the case, so stop special casing
+PF_IO_WORKER in the freezer.
+
+Signed-off-by: Jens Axboe <axboe@kernel.dk>
+Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
+---
+ kernel/freezer.c | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+--- a/kernel/freezer.c
++++ b/kernel/freezer.c
+@@ -134,7 +134,7 @@ bool freeze_task(struct task_struct *p)
+ return false;
+ }
+
+- if (!(p->flags & (PF_KTHREAD | PF_IO_WORKER)))
++ if (!(p->flags & PF_KTHREAD))
+ fake_signal_wake_up(p);
+ else
+ wake_up_state(p, TASK_INTERRUPTIBLE);
driver-core-clear-deferred-probe-reason-on-probe-retry.patch
drivers-video-fbcon-fix-null-dereference-in-fbcon_cursor.patch
riscv-evaluate-put_user-arg-before-enabling-user-access.patch
+revert-kernel-freezer-should-treat-pf_io_worker-like-pf_kthread-for-freezing.patch