linux-api.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Pirko <jiri@resnulli.us>
To: Lubomir Rintel <lkundrak@v3.sk>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-api@vger.kernel.org,
	"David S. Miller" <davem@davemloft.net>,
	Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>
Subject: Re: [PATCH] ipv6: expose RFC4191 route preference via rtnetlink
Date: Tue, 10 Mar 2015 17:04:23 +0100	[thread overview]
Message-ID: <20150310160423.GC2016@nanopsycho.orion> (raw)
In-Reply-To: <1426003013.3963.33.camel@v3.sk>

Tue, Mar 10, 2015 at 04:56:53PM CET, lkundrak@v3.sk wrote:
>On Tue, 2015-03-03 at 16:17 +0100, Jiri Pirko wrote:
>> Tue, Mar 03, 2015 at 11:01:52AM CET, lkundrak@v3.sk wrote:
>> >This makes it possible to retain the route preference when RAs are handled in
>> >userspace.
>> >
>> >Signed-off-by: Lubomir Rintel <lkundrak@v3.sk>
>> >---
>> > include/uapi/linux/rtnetlink.h |  1 +
>> > net/ipv6/route.c               | 16 +++++++++++++++-
>> > 2 files changed, 16 insertions(+), 1 deletion(-)
>> >
>> >diff --git a/include/uapi/linux/rtnetlink.h b/include/uapi/linux/rtnetlink.h
>> >index 5cc5d66..0671524 100644
>> >--- a/include/uapi/linux/rtnetlink.h
>> >+++ b/include/uapi/linux/rtnetlink.h
>> >@@ -303,6 +303,7 @@ enum rtattr_type_t {
>> > 	RTA_TABLE,
>> > 	RTA_MARK,
>> > 	RTA_MFC_STATS,
>> >+	RTA_PREF,
>> > 	__RTA_MAX
>> > };
>> > 
>> >diff --git a/net/ipv6/route.c b/net/ipv6/route.c
>> >index 47b5109..08f689e 100644
>> >--- a/net/ipv6/route.c
>> >+++ b/net/ipv6/route.c
>> >@@ -2401,6 +2401,7 @@ static const struct nla_policy rtm_ipv6_policy[RTA_MAX+1] = {
>> > 	[RTA_PRIORITY]          = { .type = NLA_U32 },
>> > 	[RTA_METRICS]           = { .type = NLA_NESTED },
>> > 	[RTA_MULTIPATH]		= { .len = sizeof(struct rtnexthop) },
>> >+	[RTA_PREF]              = { .type = NLA_U8 },
>> > };
>> > 
>> > static int rtm_to_fib6_config(struct sk_buff *skb, struct nlmsghdr *nlh,
>> >@@ -2408,6 +2409,7 @@ static int rtm_to_fib6_config(struct sk_buff *skb, struct nlmsghdr *nlh,
>> > {
>> > 	struct rtmsg *rtm;
>> > 	struct nlattr *tb[RTA_MAX+1];
>> >+	unsigned int pref;
>> > 	int err;
>> > 
>> > 	err = nlmsg_parse(nlh, sizeof(*rtm), tb, RTA_MAX, rtm_ipv6_policy);
>> >@@ -2483,6 +2485,14 @@ static int rtm_to_fib6_config(struct sk_buff *skb, struct nlmsghdr *nlh,
>> > 		cfg->fc_mp_len = nla_len(tb[RTA_MULTIPATH]);
>> > 	}
>> > 
>> >+	if (tb[RTA_PREF]) {
>> >+		pref = nla_get_u8(tb[RTA_PREF]);
>> >+		if (pref == ICMPV6_ROUTER_PREF_LOW ||
>> >+		    pref == ICMPV6_ROUTER_PREF_MEDIUM ||
>> >+		    pref == ICMPV6_ROUTER_PREF_HIGH)
>> >+			cfg->fc_flags |= RTF_PREF(pref);
>> 
>> Don't we want to do "goto errout;" in case pref is invalid ?
>
>I'm not sure. If RFC 4191 suggests that the invalid value ought to be
>ignored (treated as medium). It could be done in the userspace or the
>userspace could just relay whatever it got in the NDP message to the
>kernel.

In that case I would suggest in case of invalid value to set pref to
ICMPV6_ROUTER_PREF_MEDIUM.

>
>What is your opinion on this?
>
>Thank you,
>Lubo
>

  reply	other threads:[~2015-03-10 16:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-03 10:01 [PATCH] ipv6: expose RFC4191 route preference via rtnetlink Lubomir Rintel
2015-03-03 15:17 ` Jiri Pirko
     [not found]   ` <20150303151715.GA2020-6KJVSR23iU5sFDB2n11ItA@public.gmane.org>
2015-03-10 15:56     ` Lubomir Rintel
2015-03-10 16:04       ` Jiri Pirko [this message]
     [not found]         ` <20150310160423.GC2016-6KJVSR23iU488b5SBfVpbw@public.gmane.org>
2015-03-11 14:39           ` [PATCH v2] " Lubomir Rintel
     [not found]             ` <1426084761-3303-1-git-send-email-lkundrak-NGH9Lh4a5iE@public.gmane.org>
2015-03-11 15:01               ` Jiri Pirko
2015-03-12  3:28             ` 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=20150310160423.GC2016@nanopsycho.orion \
    --to=jiri@resnulli.us \
    --cc=davem@davemloft.net \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkundrak@v3.sk \
    --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).