From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.6 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id BA6B9C3A5A2 for ; Fri, 23 Aug 2019 19:11:30 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 8DA4A20850 for ; Fri, 23 Aug 2019 19:11:30 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=comcast.net header.i=@comcast.net header.b="teTt5FIU" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2406029AbfHWTL3 (ORCPT ); Fri, 23 Aug 2019 15:11:29 -0400 Received: from resqmta-ch2-12v.sys.comcast.net ([69.252.207.44]:43700 "EHLO resqmta-ch2-12v.sys.comcast.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2405030AbfHWTL3 (ORCPT ); Fri, 23 Aug 2019 15:11:29 -0400 Received: from resomta-ch2-07v.sys.comcast.net ([69.252.207.103]) by resqmta-ch2-12v.sys.comcast.net with ESMTP id 1Eb5i1hPrvBbZ1EqGi9fnP; Fri, 23 Aug 2019 19:03:20 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=20190202a; t=1566587000; bh=etZiqvXk5GAsAW4V7yahQT3JIIyVsMviyASPsKZU0Z4=; h=Received:Received:From:To:Subject:Date:Message-ID:MIME-Version: Content-Type; b=teTt5FIUkqEndH55sBxdUSzHI5qIUiEy1j7wJYKm/15TiFZnWTkkE5neGIvpTiVd6 oE8aFqXQWK5f37035Za8EHWkRQJ9jQv29EFZVIV7nG5JxEBISuaRaitn2iqc/zW+1H qlrUVnM4l0x2n9LJBw5zBbFA7vumXSu9VEORTsEw2R22dTIRXuoQwCgorFIqm9JYy2 M2nYeBjPuFgJ1QvDS6jHJ/pn68DYZeTvOJaifAX8uPE38O4Y4cJtZHtOikxiLk0d7r SG8BKoi44/QVzo55TMu48uv1Ltfi1AGBbIWr1/X20C7qJv2dw8/An5X/jKSDrduaNV VE6ul9RA5qkhw== Received: from DireWolf ([108.49.206.201]) by resomta-ch2-07v.sys.comcast.net with ESMTPSA id 1EpwiW3QDaF9j1EpxiHvUA; Fri, 23 Aug 2019 19:03:17 +0000 X-Xfinity-VAAS: gggruggvucftvghtrhhoucdtuddrgeduvddrudegkedgudeftdcutefuodetggdotefrodftvfcurfhrohhfihhlvgemucevohhmtggrshhtqdftvghsihdpqfgfvfdppffquffrtefokffrnecuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjughrpefhvfhfjgfufffkgggtgffothesthejghdtvddtvdenucfhrhhomhepfdfuthgvvhgvucgkrggsvghlvgdfuceoiigrsggvlhgvsegtohhmtggrshhtrdhnvghtqeenucffohhmrghinhepkhgvrhhnvghlrdhorhhgnecukfhppedutdekrdegledrvddtiedrvddtudenucfrrghrrghmpehhvghlohepffhirhgvhgholhhfpdhinhgvthepuddtkedrgeelrddvtdeirddvtddupdhmrghilhhfrhhomhepiigrsggvlhgvsegtohhmtggrshhtrdhnvghtpdhrtghpthhtohepuggrnhhivghlsehiohhgvggrrhgsohigrdhnvghtpdhrtghpthhtohepnhgvthguvghvsehvghgvrhdrkhgvrhhnvghlrdhorhhgpdhrtghpthhtohepohhnvdhkudeinhhmsehgmhgrihhlrdgtohhmpdhrtghpthhtohepshgrihhfihdrkhhhrghnsehsthhrihhkrhdrihhnpdhrtghpthhtohepshhhuhhmsegtrghnnhgurhgvfidrohhrghdprhgtphhtthhopehsthgvphhhvghnsehnvghtfihorhhkphhluhhmsggvrhdrohhrghdprhgtphhtthhopehvlhgrughimhhirhduudeisehgmhgrihhlrdgtohhmnecuvehluhhsthgvrh fuihiivgeptd X-Xfinity-VMeta: sc=-100;st=legit From: "Steve Zabele" To: Cc: , , , , , , "'Stephen Hemminger'" References: <010601d53bdc$79c86dc0$6d594940$@net> <20190716070246.0745ee6f@hermes.lan> In-Reply-To: <20190716070246.0745ee6f@hermes.lan> Subject: RE: Is bug 200755 in anyone's queue?? Date: Fri, 23 Aug 2019 15:02:47 -0400 Message-ID: <01db01d559e5$64d71de0$2e8559a0$@net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AdU73y8GSy5AAiuFQ++MzGJ5eXpFdweBSl7Q Content-Language: en-us Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org 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" 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).