ubi: check kthread_should_stop() after the setting of task state
authorZhihao Cheng <chengzhihao1@huawei.com>
Mon, 1 Jun 2020 09:12:31 +0000 (17:12 +0800)
committerRichard Weinberger <richard@nod.at>
Thu, 17 Sep 2020 20:55:59 +0000 (22:55 +0200)
commitd005f8c6588efcfbe88099b6edafc6f58c84a9c1
treec3e63aef96f76c25486a0f2094f6678320222fc6
parent58f6e78a65f1fcbf732f60a7478ccc99873ff3ba
ubi: check kthread_should_stop() after the setting of task state

A detach hung is possible when a race occurs between the detach process
and the ubi background thread. The following sequences outline the race:

  ubi thread: if (list_empty(&ubi->works)...

  ubi detach: set_bit(KTHREAD_SHOULD_STOP, &kthread->flags)
              => by kthread_stop()
              wake_up_process()
              => ubi thread is still running, so 0 is returned

  ubi thread: set_current_state(TASK_INTERRUPTIBLE)
              schedule()
              => ubi thread will never be scheduled again

  ubi detach: wait_for_completion()
              => hung task!

To fix that, we need to check kthread_should_stop() after we set the
task state, so the ubi thread will either see the stop bit and exit or
the task state is reset to runnable such that it isn't scheduled out
indefinitely.

Signed-off-by: Zhihao Cheng <chengzhihao1@huawei.com>
Cc: <stable@vger.kernel.org>
Fixes: 801c135ce73d5df1ca ("UBI: Unsorted Block Images")
Reported-by: syzbot+853639d0cb16c31c7a14@syzkaller.appspotmail.com
Signed-off-by: Richard Weinberger <richard@nod.at>
drivers/mtd/ubi/wl.c