netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Steve Zabele" <zabele@comcast.net>
To: "'Steve Zabele'" <zabele@comcast.net>, <netdev@vger.kernel.org>
Cc: <shum@canndrew.org>, <vladimir116@gmail.com>,
	<saifi.khan@strikr.in>, <daniel@iogearbox.net>,
	<on2k16nm@gmail.com>,
	"'Stephen Hemminger'" <stephen@networkplumber.org>
Subject: RE: Is bug 200755 in anyone's queue??
Date: Fri, 23 Aug 2019 15:04:14 -0400	[thread overview]
Message-ID: <01dc01d559e5$9a3735b0$cea5a110$@net> (raw)
In-Reply-To: 

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:stephen@networkplumber.org] 
Sent: Tuesday, July 16, 2019 10:03 AM
To: Steve Zabele
Cc: shum@canndrew.org; vladimir116@gmail.com; saifi.khan@DataSynergy.org;
saifi.khan@strikr.in; daniel@iogearbox.net; on2k16nm@gmail.com
Subject: Re: Is bug 200755 in anyone's queue??

On Tue, 16 Jul 2019 09:43:24 -0400
"Steve Zabele" <zabele@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).


      parent reply	other threads:[~2019-08-23 19:09 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <010601d53bdc$79c86dc0$6d594940$@net>
     [not found] ` <20190716070246.0745ee6f@hermes.lan>
2019-08-23 19:02   ` Is bug 200755 in anyone's queue?? Steve Zabele
2019-08-29 19:26     ` Willem de Bruijn
2019-08-30  8:48       ` Steve Zabele
2019-08-30  8:53       ` Steve Zabele
2019-08-30  8:54       ` Eric Dumazet
2019-08-30 20:30         ` Willem de Bruijn
2019-09-03 17:55           ` Willem de Bruijn
2019-09-04 10:28             ` Steve Zabele
2019-09-04 12:00               ` Mark KEATON
2019-09-04 12:23                 ` Eric Dumazet
2019-09-04 14:23                   ` Willem de Bruijn
2019-09-04 14:51                   ` Steve Zabele
2019-09-04 15:46                     ` Willem de Bruijn
2019-09-04 19:26                       ` Eric Dumazet
2019-09-10 15:52                       ` Willem de Bruijn
2019-09-10 16:56                         ` Paolo Abeni
2019-09-10 17:10                           ` Willem de Bruijn
2019-08-23 19:04   ` Steve Zabele [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='01dc01d559e5$9a3735b0$cea5a110$@net' \
    --to=zabele@comcast.net \
    --cc=daniel@iogearbox.net \
    --cc=netdev@vger.kernel.org \
    --cc=on2k16nm@gmail.com \
    --cc=saifi.khan@strikr.in \
    --cc=shum@canndrew.org \
    --cc=stephen@networkplumber.org \
    --cc=vladimir116@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).