summaryrefslogtreecommitdiff
path: root/net
diff options
context:
space:
mode:
authorSumit Garg <sumit.garg@linaro.org>2025-02-04 13:04:18 +0530
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2025-02-27 04:30:21 -0800
commitfd9d2d6124c293e40797a080adf8a9c237efd8b8 (patch)
tree998c1efe8cc487d6e0b1c24ad732db97b9add733 /net
parent6f3edf2d50c93c58b3be6838f3d7cccb3aa8c43e (diff)
downloadlinux-fd9d2d6124c293e40797a080adf8a9c237efd8b8.tar.gz
linux-fd9d2d6124c293e40797a080adf8a9c237efd8b8.tar.bz2
linux-fd9d2d6124c293e40797a080adf8a9c237efd8b8.zip
tee: optee: Fix supplicant wait loop
commit 70b0d6b0a199c5a3ee6c72f5e61681ed6f759612 upstream. OP-TEE supplicant is a user-space daemon and it's possible for it be hung or crashed or killed in the middle of processing an OP-TEE RPC call. It becomes more complicated when there is incorrect shutdown ordering of the supplicant process vs the OP-TEE client application which can eventually lead to system hang-up waiting for the closure of the client application. Allow the client process waiting in kernel for supplicant response to be killed rather than indefinitely waiting in an unkillable state. Also, a normal uninterruptible wait should not have resulted in the hung-task watchdog getting triggered, but the endless loop would. This fixes issues observed during system reboot/shutdown when supplicant got hung for some reason or gets crashed/killed which lead to client getting hung in an unkillable state. It in turn lead to system being in hung up state requiring hard power off/on to recover. Fixes: 4fb0a5eb364d ("tee: add OP-TEE driver") Suggested-by: Arnd Bergmann <arnd@arndb.de> Cc: stable@vger.kernel.org Signed-off-by: Sumit Garg <sumit.garg@linaro.org> Reviewed-by: Arnd Bergmann <arnd@arndb.de> Reviewed-by: Jens Wiklander <jens.wiklander@linaro.org> Signed-off-by: Arnd Bergmann <arnd@arndb.de> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'net')
0 files changed, 0 insertions, 0 deletions