Hi folks, Is there a way to find out where the SO_REUSEPORT bug reported a year ago in August (and apparently has been a bug with kernels later than 4.4) is being addressed?
The bug characteristics, simple standalone test code demonstrating the bug, and an assessment of the likely location/cause of the bug within the kernel are all described here https://bugzilla.kernel.org/show_bug.cgi?id=200755 I'm really hoping this gets fixed so we can move forward on updating our kernels/Ubuntu release from our aging 4.4/16.04 release Thanks! Steve -----Original Message----- From: Stephen Hemminger [mailto:step...@networkplumber.org] Sent: Tuesday, July 16, 2019 10:03 AM To: Steve Zabele Cc: s...@canndrew.org; vladimir...@gmail.com; saifi.k...@datasynergy.org; saifi.k...@strikr.in; dan...@iogearbox.net; on2k1...@gmail.com Subject: Re: Is bug 200755 in anyone's queue?? On Tue, 16 Jul 2019 09:43:24 -0400 "Steve Zabele" <zab...@comcast.net> wrote: > I came across bug report 200755 trying to figure out why some code I had > provided to customers a while ago no longer works with the current Linux > kernel. See > > https://bugzilla.kernel.org/show_bug.cgi?id=200755 > > I've verified that, as reported, 'connect' no longer works for UDP. > Moreover, it appears it has been broken since the 4.5 kernel has been > released. > > > > It does also appear that the intended new feature of doing round robin > assignments to different UDP sockets opened with SO_REUSEPORT also does not > work as described. > > > > Since the original bug report was made nearly a year ago for the 4.14 kernel > (and the bug is also still present in the 4.15 kernel) I'm curious if anyone > is on the hook to get this fixed any time soon. > > > > I'd rather not have to do my own demultiplexing using a single socket in > user space to work around what is clearly a (maybe not so recently > introduced) kernel bug if at all possible. My code had worked just fine on > 3.X kernels, and appears to work okay up through 4.4. > Kernel developers do not use bugzilla, I forward bug reports to netdev@vger.kernel.org (after filtering).
