From: Florian Fainelli <f.fainelli@gmail.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>, olteanv@gmail.com
Cc: andrew@lunn.ch, davem@davemloft.net, idosch@idosch.org,
jiri@resnulli.us, kuba@kernel.org, netdev@vger.kernel.org,
nikolay@nvidia.com, roopa@nvidia.com, vladimir.oltean@nxp.com,
linux-next@vger.kernel.org, kvm list <kvm@vger.kernel.org>,
linux-s390 <linux-s390@vger.kernel.org>
Subject: Re: net: bridge: propagate error code and extack from br_mc_disabled_update
Date: Wed, 21 Apr 2021 11:37:25 -0700 [thread overview]
Message-ID: <3993fbf8-b409-f88f-c573-bf5b8f418a88@gmail.com> (raw)
In-Reply-To: <cfc19833-01ec-08ea-881d-4101780d1d86@de.ibm.com>
On 4/21/2021 11:35 AM, Christian Borntraeger wrote:
>
>
> On 21.04.21 20:18, Christian Borntraeger wrote:
>> Whatever version landed in next, according to bisect this broke
>> libvirt/kvms use of bridges:
>>
>>
>> # virsh start s31128001
>> error: Failed to start domain 's31128001'
>> error: Unable to add bridge virbr1 port vnet0: Operation not supported
>>
>> # grep vnet0 /var/log/libvirt/libvirtd.log
>>
>> 2021-04-21 07:43:09.453+0000: 2460: info : virNetDevTapCreate:240 :
>> created device: 'vnet0'
>> 2021-04-21 07:43:09.453+0000: 2460: debug :
>> virNetDevSetMACInternal:287 : SIOCSIFHWADDR vnet0
>> MAC=fe:bb:83:28:01:02 - Success
>> 2021-04-21 07:43:09.453+0000: 2460: error : virNetDevBridgeAddPort:633
>> : Unable to add bridge virbr1 port vnet0: Operation not supported
>> 2021-04-21 07:43:09.466+0000: 2543: debug : udevHandleOneDevice:1695 :
>> udev action: 'add': /sys/devices/virtual/net/vnet0
>>
>> Christian
>>
>
> For reference:
>
> ae1ea84b33dab45c7b6c1754231ebda5959b504c is the first bad commit
> commit ae1ea84b33dab45c7b6c1754231ebda5959b504c
> Author: Florian Fainelli <f.fainelli@gmail.com>
> Date: Wed Apr 14 22:22:57 2021 +0300
>
> net: bridge: propagate error code and extack from br_mc_disabled_update
> Some Ethernet switches might only be able to support disabling
> multicast
> snooping globally, which is an issue for example when several bridges
> span the same physical device and request contradictory settings.
> Propagate the return value of br_mc_disabled_update() such that this
> limitation is transmitted correctly to user-space.
> Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
> Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>
> Signed-off-by: David S. Miller <davem@davemloft.net>
>
> net/bridge/br_multicast.c | 28 +++++++++++++++++++++-------
> net/bridge/br_netlink.c | 4 +++-
> net/bridge/br_private.h | 3 ++-
> net/bridge/br_sysfs_br.c | 8 +-------
> 4 files changed, 27 insertions(+), 16 deletions(-)
>
> not sure if it matters this is on s390.
> A simple reproducer is virt-install, e.g.
> virt-install --name test --disk size=12 --memory=2048 --vcpus=2
> --location
> http://ports.ubuntu.com/ubuntu-ports/dists/bionic/main/installer-s390x/
Thanks, I will kick off a reproducer and let you know.
--
Florian
next prev parent reply other threads:[~2021-04-21 18:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-14 19:22 [PATCH v2 net-next] net: bridge: propagate error code and extack from br_mc_disabled_update Vladimir Oltean
2021-04-14 21:40 ` patchwork-bot+netdevbpf
2021-04-21 18:18 ` Christian Borntraeger
2021-04-21 18:35 ` Christian Borntraeger
2021-04-21 18:37 ` Florian Fainelli [this message]
2021-04-21 18:46 ` Vladimir Oltean
2021-04-21 18:54 ` Christian Borntraeger
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=3993fbf8-b409-f88f-c573-bf5b8f418a88@gmail.com \
--to=f.fainelli@gmail.com \
--cc=andrew@lunn.ch \
--cc=borntraeger@de.ibm.com \
--cc=davem@davemloft.net \
--cc=idosch@idosch.org \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nikolay@nvidia.com \
--cc=olteanv@gmail.com \
--cc=roopa@nvidia.com \
--cc=vladimir.oltean@nxp.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).