Re: Crash with SO_REUSEPORT and ef456144da8ef507c8cf504284b6042e9201a05c
From: Marc Dionne <hidden>
Date: 2016-01-19 17:08:38
Also in:
lkml
On Tue, Jan 19, 2016 at 12:31 PM, Craig Gallek [off-list ref] wrote:
I need to think about how to handle setsockopt-after-bind condition a bit more, but the NULL pointer dereference is obviously wrong. Do you have a way to easily reproduce this? I've only managed to get it to happen once so far...
The attached code reliably triggers the crash for me.
Attachments
- reuseport_crash.c [text/x-csrc] 911 bytes · preview