From: Siva Mannem <siva.mannem.lnx@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: Netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next v2] Configure bridge FDB ageing time using netlink.
Date: Mon, 16 Mar 2015 12:12:39 +0530 [thread overview]
Message-ID: <CA+CtxLTzqDh98bPQBS9AGdoi_-2=jSrnSJN3CL2bHE5nVoZ-cQ@mail.gmail.com> (raw)
In-Reply-To: <20150315.221312.1089494260964314644.davem@davemloft.net>
On Mon, Mar 16, 2015 at 7:43 AM, David Miller <davem@davemloft.net> wrote:
> From: Siva Mannem <siva.mannem.lnx@gmail.com>
> Date: Sat, 14 Mar 2015 07:10:29 +0530
>
>> This patch allows user to configure bridge's FDB ageing using
>> netlink(for ex, iproute2). Allowed range is 10 seconds to 1000000 seconds
>> as per ieee8021QBridgeFdbAgingTime.
>>
>> Signed-off-by: Siva Mannem <siva.mannem.lnx@gmail.com>
>
> The behavior of br_changelink() leaves a lot to be desired, and this
> change is making it worse.
>
> The range of the netlink attributes, the only thing that can cause
> an error, should be validated for all attributes _first_.
>
> Because right now you can have several values change state,
> then the last one has a range error, and an error is returned
> without rolling back the state.
>
> This is terrible.
>
> When this happens the user has not reliable way to figure out
> that some of the state changes it requested happened, and
> exactly which ones those were.
>
> If an error is thrown we _MUST_ not make any state changes to
> the bridge whatsoever.
Agree. Will work on it. Can it be a follow-on patch?
--
Regards,
Siva Mannem.
next prev parent reply other threads:[~2015-03-16 6:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-14 1:40 [PATCH net-next v2] Configure bridge FDB ageing time using netlink Siva Mannem
2015-03-14 6:52 ` Scott Feldman
2015-03-14 22:17 ` Scott Feldman
2015-03-14 23:36 ` Siva Mannem
2015-03-15 1:16 ` Scott Feldman
2015-03-15 4:18 ` Siva Mannem
2015-03-16 2:13 ` David Miller
2015-03-16 6:42 ` Siva Mannem [this message]
2015-03-16 16:49 ` David Miller
2015-03-16 7:59 ` Siva Mannem
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='CA+CtxLTzqDh98bPQBS9AGdoi_-2=jSrnSJN3CL2bHE5nVoZ-cQ@mail.gmail.com' \
--to=siva.mannem.lnx@gmail.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.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 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).