summaryrefslogtreecommitdiffstats
path: root/MAINTAINERS
diff options
context:
space:
mode:
authorMike Christie2010-03-31 21:41:35 +0200
committerJames Bottomley2010-04-11 20:28:13 +0200
commitd7d05548a62c87ee55b0c81933669177f885aa8d (patch)
tree9c23e54b6e843a7eed97e96073c54348d609e95f /MAINTAINERS
parent[SCSI] qla2xxx: fix lock imbalance (diff)
downloadkernel-qcow2-linux-d7d05548a62c87ee55b0c81933669177f885aa8d.tar.gz
kernel-qcow2-linux-d7d05548a62c87ee55b0c81933669177f885aa8d.tar.xz
kernel-qcow2-linux-d7d05548a62c87ee55b0c81933669177f885aa8d.zip
[SCSI] iscsi_tcp: fix relogin/shutdown hang
When I made this patch: b64e77f70b8c11766e967e3485331a9e6ef01390 it was to solve a problem where we were already on the waitqueue becuase a connection problem/logout caused us to be on there when we were cleaning up the session. If we happen to get on queue for more normal reasons like their just does not happen to be any send space at the same time we are closing the connection we hit a race and get stuck in the wait. We should not check if the waitqueue is active because we could race with the network code. If the network xmit code is just about to enter the prepare to wait when we check for the waitqueue to be active then we will miss each other and the network code will fall into the wait and we will not run wake_up. Signed-off-by: Mike Christie <michaelc@cs.wisc.edu> Signed-off-by: James Bottomley <James.Bottomley@suse.de>
Diffstat (limited to 'MAINTAINERS')
0 files changed, 0 insertions, 0 deletions