aboutsummaryrefslogtreecommitdiffstats
path: root/net/dccp
diff options
context:
space:
mode:
authorTrond Myklebust <Trond.Myklebust@netapp.com>2012-10-22 17:14:36 -0400
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2012-10-31 09:51:34 -0700
commit5b34d96acadef305c862006ce5d079dfb6526ee8 (patch)
treef3e0bf992a3273b86dd15ba94ed54bc5ab8fafcb /net/dccp
parent387373e6448530b13056d4e32dfe2a5bf15c9aaf (diff)
downloadkernel_samsung_smdk4412-5b34d96acadef305c862006ce5d079dfb6526ee8.zip
kernel_samsung_smdk4412-5b34d96acadef305c862006ce5d079dfb6526ee8.tar.gz
kernel_samsung_smdk4412-5b34d96acadef305c862006ce5d079dfb6526ee8.tar.bz2
SUNRPC: Get rid of the xs_error_report socket callback
commit f878b657ce8e7d3673afe48110ec208a29e38c4a upstream. Chris Perl reports that we're seeing races between the wakeup call in xs_error_report and the connect attempts. Basically, Chris has shown that in certain circumstances, the call to xs_error_report causes the rpc_task that is responsible for reconnecting to wake up early, thus triggering a disconnect and retry. Since the sk->sk_error_report() calls in the socket layer are always followed by a tcp_done() in the cases where we care about waking up the rpc_tasks, just let the state_change callbacks take responsibility for those wake ups. Reported-by: Chris Perl <chris.perl@gmail.com> Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com> Tested-by: Chris Perl <chris.perl@gmail.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'net/dccp')
0 files changed, 0 insertions, 0 deletions