On Mon, Aug 20, 2012 at 05:35:06PM -0500, Malahal Naineni wrote: > J. Bruce Fields [bfields@xxxxxxxxxxxx] wrote: > > From: "J. Bruce Fields" <bfields@xxxxxxxxxx> > > > > svc_tcp_sendto sets XPT_CLOSE if we fail to transmit the entire reply. > > However, the XPT_CLOSE won't be acted on immediately. Meanwhile other > > threads could send further replies before the socket is really shut > > down. ... > Instrumented svc_send_common() to send partial read replies, was able > reproduce the corruption easily. After applying this patch, I wasn't > able to reproduce the corruption. The patch looks good. I wonder, maybe someone who understands the tcp code better could answer: is it really possible for a sendto to fail and then a subsequent send succeed? If so, what are possible causes? I'm curious how we'd reproduce this without the artificial fault injection. --b. -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
