From: roopa <roopa@cumulusnetworks.com>
To: David Miller <davem@davemloft.net>
Cc: nicolas.dichtel@6wind.com, mkubecek@suse.cz,
Mazziesaccount@gmail.com, hannes@stressinduktion.org,
kuznet@ms2.inr.ac.ru, jmorris@namei.org, yoshfuji@linux-ipv6.org,
netdev@vger.kernel.org
Subject: Re: [PATCH net v4] ipv6: fix multipath route replace error recovery
Date: Wed, 09 Sep 2015 22:08:03 -0700 [thread overview]
Message-ID: <55F11033.6090303@cumulusnetworks.com> (raw)
In-Reply-To: <20150909.141059.1681588831579060449.davem@davemloft.net>
On 9/9/15, 2:10 PM, David Miller wrote:
> From: Roopa Prabhu <roopa@cumulusnetworks.com>
> Date: Tue, 8 Sep 2015 10:53:04 -0700
>
>> This patch reduces the possibility of this by doing the following:
>> a) Changes the existing multipath route add code to a two stage process:
>> build rt6_infos + insert them
>> ip6_route_add rt6_info creation code is moved into
>> ip6_route_info_create.
>> b) This ensures that most errors are caught during building rt6_infos
>> and we fail early
>> c) Separates multipath add and del code. Because add needs the special
>> two stage mode in a) and delete essentially does not care.
>> d) In any event if the code fails during inserting a route again, a
>> warning is printed (This should be unlikely)
> Looks good, follows the usual "prepare/commit" paradigm.
>
> Applied, thanks.
>
> For net-next, it might be nice to make ip6_route_info_create() return
> error pointers instead of returning the rt pointer by reference.
ok, sounds good. Will post a patch with the error pointer to next-next
when it opens. thanks.
prev parent reply other threads:[~2015-09-10 5:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-08 17:53 [PATCH net v4] ipv6: fix multipath route replace error recovery Roopa Prabhu
2015-09-08 19:59 ` Nikolay Aleksandrov
2015-09-09 10:05 ` Nicolas Dichtel
2015-09-09 21:10 ` David Miller
2015-09-10 5:08 ` roopa [this message]
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=55F11033.6090303@cumulusnetworks.com \
--to=roopa@cumulusnetworks.com \
--cc=Mazziesaccount@gmail.com \
--cc=davem@davemloft.net \
--cc=hannes@stressinduktion.org \
--cc=jmorris@namei.org \
--cc=kuznet@ms2.inr.ac.ru \
--cc=mkubecek@suse.cz \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
--cc=yoshfuji@linux-ipv6.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