From: David Miller <davem@davemloft.net>
To: dlezcano@fr.ibm.com
Cc: yoshfuji@linux-ipv6.org, pekkas@netcore.fi,
netdev@vger.kernel.org, benjamin.thery@bull.net
Subject: Re: [patch 5/6] ipv6 - make af_inet6 to check ip6_route_init return value
Date: Fri, 07 Dec 2007 00:44:39 -0800 (PST) [thread overview]
Message-ID: <20071207.004439.09626888.davem@davemloft.net> (raw)
In-Reply-To: <20071206140307.686276824@ICON-9-164-138-215.megacenter.de.ibm.com>
From: Daniel Lezcano <dlezcano@fr.ibm.com>
Date: Thu, 06 Dec 2007 14:53:34 +0100
> The af_inet6 initialization function does not check the return code
> of the route initilization, so if something goes wrong, the protocol
> initialization will continue anyway.
> This patch takes into account the modification made in the different
> route's initialization subroutines to check the return value and to
> make the protocol initialization to fail.
>
> Signed-off-by: Daniel Lezcano <dlezcano@fr.ibm.com>
> Acked-by: Benjamin Thery <benjamin.thery@bull.net>
Applied, thanks!
next prev parent reply other threads:[~2007-12-07 8:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-06 13:53 [patch 0/6] ipv6 - ipv6 routing initialization Daniel Lezcano
2007-12-06 13:53 ` [patch 1/6] ipv6 - make fib6_init to return an error code Daniel Lezcano
2007-12-07 8:41 ` David Miller
2007-12-06 13:53 ` [patch 2/6] ipv6 - make xfrm6_init " Daniel Lezcano
2007-12-07 8:42 ` David Miller
2007-12-06 13:53 ` [patch 3/6] ipv6 - make fib6_rules_init " Daniel Lezcano
2007-12-07 8:43 ` David Miller
2007-12-06 13:53 ` [patch 4/6] ipv6 - make ip6_route_init " Daniel Lezcano
2007-12-07 8:43 ` David Miller
2007-12-06 13:53 ` [patch 5/6] ipv6 - make af_inet6 to check ip6_route_init return value Daniel Lezcano
2007-12-07 8:44 ` David Miller [this message]
2007-12-06 13:53 ` [patch 6/6] ipv6 - route6/fib6 : dont panic a kmem_cache_create Daniel Lezcano
2007-12-07 8:45 ` 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=20071207.004439.09626888.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=benjamin.thery@bull.net \
--cc=dlezcano@fr.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=pekkas@netcore.fi \
--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;
as well as URLs for NNTP newsgroup(s).