From: roopa <roopa@cumulusnetworks.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
David Miller <davem@davemloft.net>,
rshearma@brocade.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next] mpls: Don't accept multipath configuration until the support is complete
Date: Tue, 03 Nov 2015 06:03:02 -0800 [thread overview]
Message-ID: <5638BE96.2010700@cumulusnetworks.com> (raw)
In-Reply-To: <87ziyvr4w2.fsf@x220.int.ebiederm.org>
On 11/2/15, 10:09 PM, Eric W. Biederman wrote:
> Sergei Shtylyov <sergei.shtylyov@cogentembedded.com> writes:
>
>> Hello.
>>> diff --git a/net/mpls/af_mpls.c b/net/mpls/af_mpls.c
>>> index c70d750148b6..893cd2dc3979 100644
>>> --- a/net/mpls/af_mpls.c
>>> +++ b/net/mpls/af_mpls.c
>>> @@ -1162,6 +1162,8 @@ static int rtm_to_route_config(struct sk_buff *skb, struct nlmsghdr *nlh,
>>> {
>>> cfg->rc_mp = nla_data(nla);
>>> cfg->rc_mp_len = nla_len(nla);
>>> + /* Fail until multipath support is complete */
>>> + goto errout;
>>> break;
>> Forgot to delete *break*?
> Nope. I did that deliberately, because this code is not supposed to
> stay this way for long.
Eric, this is only until dead route support is added correct ?.
If yes, then my v2 on dead route/nh support is out. I know david is only taking bug fixes right now...
and I thought the dead route/nh is a bug fix. If you are ok with v2, we could skip this patch ?.
If david decides to not pick it up in net-next, i was hoping to submit it as a bug-fix to net.
next prev parent reply other threads:[~2015-11-03 14:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-29 15:49 [PATCH net-next RFC] mpls: support for dead routes Roopa Prabhu
2015-10-29 16:53 ` Robert Shearman
2015-10-29 18:46 ` roopa
2015-10-30 15:06 ` Robert Shearman
2015-11-01 21:24 ` Eric W. Biederman
2015-11-01 21:27 ` Eric W. Biederman
2015-11-02 1:01 ` roopa
2015-11-02 5:08 ` Eric W. Biederman
2015-11-02 21:18 ` roopa
2015-11-02 19:29 ` [PATCH net-next] mpls: Don't accept multipath configuration until the support is complete Eric W. Biederman
2015-11-02 19:49 ` Sergei Shtylyov
2015-11-03 6:09 ` Eric W. Biederman
2015-11-03 14:03 ` roopa [this message]
2015-11-03 15:14 ` Robert Shearman
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=5638BE96.2010700@cumulusnetworks.com \
--to=roopa@cumulusnetworks.com \
--cc=davem@davemloft.net \
--cc=ebiederm@xmission.com \
--cc=netdev@vger.kernel.org \
--cc=rshearma@brocade.com \
--cc=sergei.shtylyov@cogentembedded.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).