From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Hemminger Subject: Fw: [Bug 201071] New: Creating a vxlan in state 'up' does not give proper RTM_NEWLINK message Date: Mon, 10 Sep 2018 11:55:16 -0700 Message-ID: <20180910115516.46f0c47d@shemminger-XPS-13-9360> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: netdev@vger.kernel.org To: Roopa Prabhu Return-path: Received: from mail-pf1-f181.google.com ([209.85.210.181]:38800 "EHLO mail-pf1-f181.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726755AbeIJXuu (ORCPT ); Mon, 10 Sep 2018 19:50:50 -0400 Received: by mail-pf1-f181.google.com with SMTP id x17-v6so10934996pfh.5 for ; Mon, 10 Sep 2018 11:55:22 -0700 (PDT) Sender: netdev-owner@vger.kernel.org List-ID: Begin forwarded message: Date: Mon, 10 Sep 2018 04:04:37 +0000 From: bugzilla-daemon@bugzilla.kernel.org To: stephen@networkplumber.org Subject: [Bug 201071] New: Creating a vxlan in state 'up' does not give proper RTM_NEWLINK message https://bugzilla.kernel.org/show_bug.cgi?id=201071 Bug ID: 201071 Summary: Creating a vxlan in state 'up' does not give proper RTM_NEWLINK message Product: Networking Version: 2.5 Kernel Version: 4.19-rc1 Hardware: All OS: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Other Assignee: stephen@networkplumber.org Reporter: liam.mcbirnie@boeing.com Regression: Yes If a vxlan is created with state 'up', the RTM_NEWLINK message shows the state as down, and there no other netlink messages are sent. As a result, processes listening to netlink are never notified that the vxlan link is up. eg. # ip link add test up type vxlan id 8 group 224.224.224.224 dev eth0 Output of ip monitor link # 4: test: mtu 1450 qdisc noop state DOWN group default link/ether ee:cd:97:1a:cf:91 brd ff:ff:ff:ff:ff:ff Output of ip link show (expected from netlink message) # 4: test: mtu 1450 qdisc noqueue state UNKNOWN group default qlen 1000 link/ether ee:cd:97:1a:cf:91 brd ff:ff:ff:ff:ff:ff This is a regression introduced by the following patch series. https://patchwork.ozlabs.org/patch/947181/ -- You are receiving this mail because: You are the assignee for the bug.