Rather than manually waking up any context sleeping on the sock to
signal an error we should call sk_error_report(). This has the added
benefit that in-kernel consumers can override this notification with
its own callback.

Signed-off-by: Bjorn Andersson <bjorn.anders...@linaro.org>
---
 net/qrtr/qrtr.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/net/qrtr/qrtr.c b/net/qrtr/qrtr.c
index c2f5c13550c0..7e4b49a8349e 100644
--- a/net/qrtr/qrtr.c
+++ b/net/qrtr/qrtr.c
@@ -541,7 +541,7 @@ static void qrtr_reset_ports(void)
 
                sock_hold(&ipc->sk);
                ipc->sk.sk_err = ENETRESET;
-               wake_up_interruptible(sk_sleep(&ipc->sk));
+               ipc->sk.sk_error_report(&ipc->sk);
                sock_put(&ipc->sk);
        }
        mutex_unlock(&qrtr_port_lock);
-- 
2.12.0

Reply via email to