IrDA: Correctly handling socket error
Subsystems (2)
PATCH 1/1 IrDA: Correctly handling socket error
From: Olaf Kirch <[email protected]>
This patch fixes an oops first reported in mid 2006 - see
http://lkml.org/lkml/2006/8/29/358 The cause of this bug report is that when an error is signalled on the socket, irda_recvmsg_stream returns without removing a local wait_queue variable from the socket's sk_sleep queue. This causes havoc further down the road.
In response to this problem, a patch was made that invoked sock_orphan on the socket when receiving a disconnect indication. This is not a good fix, as this sets sk_sleep to NULL, causing applications sleeping in recvmsg (and other places) to oops.
This is against the latest net-2.6 and should be considered for -stable inclusion.
--- net/irda/af_irda.c | 3 +-- 1 files changed, 1 insertions(+), 2 deletions(-)
net/irda/af_irda.c +1 -2
@@ -138,7 +138,6 @@ static void irda_disconnect_indication(void *instance, void *sap, sk->sk_shutdown |=SEND_SHUTDOWN ; sk->sk_state_change (sk); -sock_orphan (sk);release_sock (sk);/* Close our TSAP.
@@ -1445,7 +1444,7 @@ static int irda_recvmsg_stream(struct kiocb *iocb, struct socket *sock,*/ ret =sock_error (sk);if (ret) -break ; + ;else if (sk->sk_shutdown &RCV_SHUTDOWN ) ;else if (noblock)
Signature · 9 lines
1.5.1 ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/
David Miller
maintainerFrom: Samuel Ortiz <[email protected]>
Date: Thu, 19 Apr 2007 00:45:26 +0300
Quoted 13 lines
From: Olaf Kirch <[email protected]>
This patch fixes an oops first reported in mid 2006 - see
http://lkml.org/lkml/2006/8/29/358 The cause of this bug report is that when an error is signalled on the socket,irda_recvmsg_streamreturns without removing a localwait_queuevariable from the socket'ssk_sleepqueue. This causes havoc further down the road.In response to this problem, a patch was made that invoked
sock_orphanon the socket when receiving a disconnect indication. This is not a good fix, as this setssk_sleepto NULL, causing applications sleeping in recvmsg (and other places) to oops.
Quoted 5 lines
This is against the latest net-2.6 and should be considered for -stable inclusion.
Signed-off-by Olaf Kirch <[email protected]>Signed-off-by Samuel Ortiz <[email protected]>
Applied and I'll push this to -stable too, thanks!