* Fw: [Bug 201071] New: Creating a vxlan in state 'up' does not give proper RTM_NEWLINK message
@ 2018-09-10 18:55 Stephen Hemminger
2018-09-11 22:10 ` Roopa Prabhu
0 siblings, 1 reply; 3+ messages in thread
From: Stephen Hemminger @ 2018-09-10 18:55 UTC (permalink / raw)
To: Roopa Prabhu; +Cc: netdev
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.
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: Fw: [Bug 201071] New: Creating a vxlan in state 'up' does not give proper RTM_NEWLINK message
2018-09-10 18:55 Fw: [Bug 201071] New: Creating a vxlan in state 'up' does not give proper RTM_NEWLINK message Stephen Hemminger
@ 2018-09-11 22:10 ` Roopa Prabhu
2018-09-12 4:48 ` Roopa Prabhu
0 siblings, 1 reply; 3+ messages in thread
From: Roopa Prabhu @ 2018-09-11 22:10 UTC (permalink / raw)
To: Stephen Hemminger; +Cc: netdev
On Mon, Sep 10, 2018 at 11:55 AM, Stephen Hemminger
<stephen@networkplumber.org> wrote:
>
>
> 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.
thanks for the fwd. looking...
>
> 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.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Fw: [Bug 201071] New: Creating a vxlan in state 'up' does not give proper RTM_NEWLINK message
2018-09-11 22:10 ` Roopa Prabhu
@ 2018-09-12 4:48 ` Roopa Prabhu
0 siblings, 0 replies; 3+ messages in thread
From: Roopa Prabhu @ 2018-09-12 4:48 UTC (permalink / raw)
To: Stephen Hemminger; +Cc: netdev
On Tue, Sep 11, 2018 at 3:10 PM, Roopa Prabhu <roopa@cumulusnetworks.com> wrote:
> On Mon, Sep 10, 2018 at 11:55 AM, Stephen Hemminger
> <stephen@networkplumber.org> wrote:
>>
>>
>> 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.
>
> thanks for the fwd. looking...
>
>
attached a patch to the bug. Will post it here after some confirmation
of the fix from the reporter.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2018-09-12 9:51 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2018-09-10 18:55 Fw: [Bug 201071] New: Creating a vxlan in state 'up' does not give proper RTM_NEWLINK message Stephen Hemminger
2018-09-11 22:10 ` Roopa Prabhu
2018-09-12 4:48 ` Roopa Prabhu
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox