All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brian Haley <brian.haley@hp.com>
To: Lorenzo Colitti <lorenzo@google.com>
Cc: maze@google.com, yoshfuji@linux-ipv6.org, netdev@vger.kernel.org,
	c@google.com
Subject: Re: [PATCH] net: ipv6: Allow netlink to set IPv6 address scope
Date: Mon, 10 Oct 2011 12:16:06 -0400	[thread overview]
Message-ID: <4E931A46.1040905@hp.com> (raw)
In-Reply-To: <20111005201559.E544016A599@drone1.mtv.corp.google.com>

On 10/05/2011 04:15 PM, Lorenzo Colitti wrote:
> net: ipv6: Allow netlink to set IPv6 address scope
> 
> Currently, userspace cannot specify the scope of IPv6
> addresses when creating or modifying them. Instead, the
> scope is automatically determined from the address itself.
> In IPv4, userspace can set whatever scope it likes.
> 
> Allow userspace to specify the scope of IPv6 addresses in
> a backwards-compatible way: if the scope passed in is zero,
> use the old behaviour of automatically determining the
> scope based on the address.
> 
> Signed-off-by: Lorenzo Colitti <lorenzo@google.com>

Hi Lorenzo,

I remember someone proposing a similar patch before and it was not accepted, do
you have a use case for doing this?  It just seems like it will cause problems.

Also, there are other parts of the kernel (NFS, SCTP, IPv6 multicast) that are
still calling ipv6_addr_scope() on a plain address - won't those be broken since
they'll return the correct, RFC-implied scope?

-Brian

  reply	other threads:[~2011-10-10 16:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-05 20:15 [PATCH] net: ipv6: Allow netlink to set IPv6 address scope Lorenzo Colitti
2011-10-10 16:16 ` Brian Haley [this message]
2011-10-13 23:55   ` Lorenzo Colitti
2011-10-14 20:14     ` Brian Haley
2011-10-14 22:32       ` Lorenzo Colitti
2011-10-17  0:45         ` Brian Haley
2011-10-17  2:26           ` Lorenzo Colitti
2011-10-17 21:32             ` Brian Haley
2011-10-21  4:25               ` Maciej Żenczykowski

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=4E931A46.1040905@hp.com \
    --to=brian.haley@hp.com \
    --cc=c@google.com \
    --cc=lorenzo@google.com \
    --cc=maze@google.com \
    --cc=netdev@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.