Messages in this thread | | | Date | Sun, 11 Jul 2010 00:11:20 -0300 | Subject | Re: [PATCH] tproxy: nf_tproxy_assign_sock() can handle tw sockets | From | Felipe W Damasio <> |
| |
Hi Mr. Miller,
2010/7/10 David Miller <davem@davemloft.net>: > It could be corruption from elsewhere. Those last four hex > digits (0x5d415d41) are "]A]A" in ascii, but that could just > be coincidence.
What do you mean "from elsewhere"? You mean elsewhere on the network code?
Since the function that had the problem was tcp_recvmsg and we're talking about a squid process, we're either talking about a typical webserver-objet response, or about about an incorrect/faulty http request from the user.
Like I told Mr. Dumazet, since on the squid logs I got a:
2010/07/08 14:51:10| clientTryParseRequest: FD 6088 (187.16.240.122:2035) Invalid Request
Only a second before the bug entry on syslog, I suppose that this invalid request caused the problem (more like a guess, really).
If you think there's a way I can help reproduce/trigger and fix this bug, please let me know, since the production machine is down until I can ensure my bosses that this particular crash won't happen again.
Thanks,
Felipe Damasio -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |