All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roman Mashak <mrv@mojatatu.com>
To: David Ahern <dsahern@gmail.com>
Cc: David Miller <davem@davemloft.net>,
	Stephen Hemminger <stephen@networkplumber.org>,
	Linux Kernel Network Developers <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next v2 1/1] bridge: return error code when deleting Vlan
Date: Thu, 12 Oct 2017 14:07:20 -0400	[thread overview]
Message-ID: <CAHvchGnVZaSq+s9953jdbf6-UzDFb36457U6Pk0oQHgVOKwzQg@mail.gmail.com> (raw)
In-Reply-To: <fef6f65d-473c-ee8e-51cc-1382cb6f84b9@gmail.com>

On Thu, Oct 12, 2017 at 10:19 AM, David Ahern <dsahern@gmail.com> wrote:
> On 10/12/17 7:51 AM, Roman Mashak wrote:
>> v2:
>>  Return err immediately if nbp_vlan_delete() fails (pointed by David Ahern)
>>
>> Signed-off-by: Roman Mashak <mrv@mojatatu.com>
>> ---
>>  net/bridge/br_netlink.c | 8 +++++---
>>  1 file changed, 5 insertions(+), 3 deletions(-)
>>
>> diff --git a/net/bridge/br_netlink.c b/net/bridge/br_netlink.c
>> index f0e8268..1efdd48 100644
>> --- a/net/bridge/br_netlink.c
>> +++ b/net/bridge/br_netlink.c
>> @@ -527,11 +527,13 @@ static int br_vlan_info(struct net_bridge *br, struct net_bridge_port *p,
>>
>>       case RTM_DELLINK:
>>               if (p) {
>> -                     nbp_vlan_delete(p, vinfo->vid);
>> +                     err = nbp_vlan_delete(p, vinfo->vid);
>> +                     if (err)
>> +                             break;
>
> I'm not sure a break is the right thing to do. Seems like you leave it
> in a half configured state.
>
>>                       if (vinfo->flags & BRIDGE_VLAN_INFO_MASTER)
>> -                             br_vlan_delete(p->br, vinfo->vid);
>> +                             err = br_vlan_delete(p->br, vinfo->vid);
>>               } else {
>> -                     br_vlan_delete(br, vinfo->vid);
>> +                     err = br_vlan_delete(br, vinfo->vid);
>>               }
>>               break;
>>       }
>>
>
> Why do you want to return the error code here? Walking the code paths
> seems like ENOENT or err from switchdev_port_obj_del are the 2 error
> possibilities.

For example, if you attempt to delete a non-existing vlan on a port,
the current code succeeds and also sends event :

rtnetlink_rcv_msg
    rtnl_bridge_dellink
       br_dellink
          br_afspec
             br_vlan_info

int br_dellink(..)
{
  ...
  err = br_afspec()
  if (err == 0)
      br_ifinfo_notify(RTM_NEWLINK, p);
}

This is misleading, so a proper errcode has to be produced.

  reply	other threads:[~2017-10-12 18:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-12 13:51 [PATCH net-next v2 1/1] bridge: return error code when deleting Vlan Roman Mashak
2017-10-12 14:19 ` David Ahern
2017-10-12 18:07   ` Roman Mashak [this message]
2017-10-12 18:12     ` Nikolay Aleksandrov
2017-10-13  2:03       ` Jamal Hadi Salim
2017-10-13  2:15         ` Nikolay Aleksandrov
2017-10-13 14:31           ` David Ahern
2017-10-13 16:00       ` Roman Mashak
2017-10-14 10:52         ` Nikolay Aleksandrov

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=CAHvchGnVZaSq+s9953jdbf6-UzDFb36457U6Pk0oQHgVOKwzQg@mail.gmail.com \
    --to=mrv@mojatatu.com \
    --cc=davem@davemloft.net \
    --cc=dsahern@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=stephen@networkplumber.org \
    /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.