From: David Ahern <dsahern@gmail.com>
To: sfeldma@gmail.com, netdev@vger.kernel.org
Cc: jiri@resnulli.us, bblanco@plumgrid.com
Subject: Re: [PATCH net-next] switchdev: fix BUG when port driver doesn't support set attr op
Date: Wed, 10 Jun 2015 15:25:16 -0600 [thread overview]
Message-ID: <5578AB3C.5020206@gmail.com> (raw)
In-Reply-To: <1433969762-22406-1-git-send-email-sfeldma@gmail.com>
On 6/10/15 2:56 PM, sfeldma@gmail.com wrote:
> From: Scott Feldman <sfeldma@gmail.com>
>
> Fix a BUG() where CONFIG_NET_SWITCHDEV is set but the driver for a bridged
> port does not support switchdec_port_attr_set op. Don't BUG() if
> -EOPNOTSUPP is returned.
>
> Signed-off-by: Scott Feldman <sfeldma@gmail.com>
> Reported-by: Brenden Blanco <bblanco@plumgrid.com>
> ---
> net/switchdev/switchdev.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/net/switchdev/switchdev.c b/net/switchdev/switchdev.c
> index e008057..99bced4 100644
> --- a/net/switchdev/switchdev.c
> +++ b/net/switchdev/switchdev.c
> @@ -103,7 +103,7 @@ static void switchdev_port_attr_set_work(struct work_struct *work)
>
> rtnl_lock();
> err = switchdev_port_attr_set(asw->dev, &asw->attr);
> - BUG_ON(err);
> + BUG_ON(err && err != -EOPNOTSUPP);
> rtnl_unlock();
>
> dev_put(asw->dev);
>
Should that be WARN_ON instead of BUG_ON?
next prev parent reply other threads:[~2015-06-10 21:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-10 20:56 [PATCH net-next] switchdev: fix BUG when port driver doesn't support set attr op sfeldma
2015-06-10 21:13 ` Andy Gospodarek
2015-06-10 21:25 ` David Ahern [this message]
2015-06-10 21:47 ` Scott Feldman
2015-06-10 21:51 ` David Ahern
2015-06-10 22:00 ` Scott Feldman
2015-06-11 6:16 ` Jiri Pirko
2015-06-11 15:03 ` Scott Feldman
2015-06-11 15:34 ` Jiri Pirko
2015-06-11 7:06 ` David Miller
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=5578AB3C.5020206@gmail.com \
--to=dsahern@gmail.com \
--cc=bblanco@plumgrid.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=sfeldma@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.