From: Stephen Hemminger <stephen@networkplumber.org>
To: Roopa Prabhu <roopa@cumulusnetworks.com>
Cc: netdev@vger.kernel.org
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 [thread overview]
Message-ID: <20180910115516.46f0c47d@shemminger-XPS-13-9360> (raw)
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: <BROADCAST,MULTICAST> 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: <BROADCAST,MULTICAST,UP,LOWER_UP> 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.
next reply other threads:[~2018-09-10 23:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-10 18:55 Stephen Hemminger [this message]
2018-09-11 22:10 ` Fw: [Bug 201071] New: Creating a vxlan in state 'up' does not give proper RTM_NEWLINK message Roopa Prabhu
2018-09-12 4:48 ` Roopa Prabhu
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=20180910115516.46f0c47d@shemminger-XPS-13-9360 \
--to=stephen@networkplumber.org \
--cc=netdev@vger.kernel.org \
--cc=roopa@cumulusnetworks.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