Hi David,
I'm able to reproduce it, so I'd be happy to test your fix.
Thanks!
On Wed, Nov 2, 2016 at 7:31 PM, David Ahern [off-list ref] wrote:
On 11/2/16 11:21 AM, Eric Dumazet wrote:
quoted
Thanks for your report.
David, please take a look.
TCP MD5 can call __inet_lookup_listener() with a NULL skb.
interesting. I did not test md5 before sending, but doing so now I am not able to trigger the panic with any combination of passwords - correct, wrong, none, no listener, etc. perhaps I am missing a sysctl setting.
Will send a fix. I see the call to __inet_lookup_listener with null skb.
quoted
Bug added in commit a04a480d4392ea6efd117be2de564117b2a009c0