From: Chuck Lever <chuck.lever@oracle.com>
To: Brian Haley <brian.haley@hp.com>
Cc: Jay Vosburgh <fubar@us.ibm.com>,
David Miller <davem@davemloft.net>,
arvidjaar@mail.ru, vladislav.yasevich@hp.com, tytso@mit.edu,
Valdis.Kletnieks@vt.edu, rjw@sisk.pl, netdev@vger.kernel.org,
bonding-devel@lists.sourceforge.net, jamagallon@ono.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] bonding: move IPv6 support into a separate kernel module
Date: Thu, 26 Feb 2009 14:41:36 -0500 [thread overview]
Message-ID: <F613EEFD-2332-4C75-A486-73CDF2BAADDE@oracle.com> (raw)
In-Reply-To: <49A6ED6D.3090508@hp.com>
On Feb 26, 2009, at Feb 26, 2009, 2:28 PM, Brian Haley wrote:
> Jay Vosburgh wrote:
>>>>> I've been fooling with the disable_ipv6 sysctl, and one issue is
>>>>> that, at least on the distro I'm testing on (SLES), it's not
>>>>> picked up
>>>>> from /etc/sysctl.conf at boot time (presumably because ipv6
>>>>> isn't loaded
>>>>> yet, although I haven't really checked).
>>>> Correct, that's the problem.
>>>>
>>>> We could create a blocker bitmap. Two sysctls, "block_af" and
>>>> "unblock_af". You write the AF_foo value for the protocol there
>>>> and
>>>> it sets or clears the assosciated bit in the internal blocker
>>>> bitmap.
>>>>
>>>> Things like sys_socket() et al. key off of this.
>>> I'm open to suggestions at this point in time, I just don't see
>>> how this
>>> will solve the bonding problem since it still wouldn't load, right?
>> It would permit users to load ipv6 (thus allowing bonding to
>> load), but prevent ipv6 from actually doing anything. (because
>> sys_socket, e.g., won't open an ipv6 socket if block_af includes
>> ipv6).
>
> Right, but it doesn't help someone that changed /etc/modprobe.conf
> to have "install ipv6 /bin/true" - they'll have to stop doing that.
>
> I think changing ipv6 to support a disable_ipv6 module parameter
> like Vlad suggested would work, as long as we're not worried about
> someone opening an AF_INET6 socket - even if they do they won't get
> anywhere.
In this case, if IPV6ONLY is set on an AF_INET6 listener, it should
still get AF_INET traffic, correct?
> That, along with the patch below to actually not add the addresses,
> would work (sorry in advance for using an attachment). I'll get
> started on that...
>
> -Brian
>
>
> --
>
> The disable_ipv6 knob was meant to be used for the kernel to disable
> IPv6 on an interface when DAD failed for the link-local address
> based on the MAC, but we should also be able to administratively
> disable it on an interface, or the entire system. This patch fixes
> the per-interface problem.
>
> Signed-off-by: Brian Haley <brian.haley@hp.com>
> diff --git a/net/ipv6/addrconf.c b/net/ipv6/addrconf.c
> index f8f76d6..90f2a81 100644
> --- a/net/ipv6/addrconf.c
> +++ b/net/ipv6/addrconf.c
> @@ -603,6 +603,11 @@ ipv6_add_addr(struct inet6_dev *idev, const
> struct in6_addr *addr, int pfxlen,
> goto out2;
> }
>
> + if (idev->cnf.disable_ipv6) {
> + err = -EPERM;
> + goto out2;
> + }
> +
> write_lock(&addrconf_hash_lock);
>
> /* Ignore adding duplicate addresses on an interface */
--
Chuck Lever
chuck[dot]lever[at]oracle[dot]com
next prev parent reply other threads:[~2009-02-26 19:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-25 20:44 [PATCH v2] bonding: move IPv6 support into a separate kernel module Brian Haley
2009-02-25 22:10 ` Jay Vosburgh
2009-02-25 22:14 ` David Miller
2009-02-26 16:44 ` Brian Haley
2009-02-26 18:14 ` Jay Vosburgh
2009-02-26 18:38 ` Vlad Yasevich
2009-02-26 19:49 ` Jay Vosburgh
2009-02-26 19:28 ` Brian Haley
2009-02-26 19:41 ` Chuck Lever [this message]
2009-02-26 19:59 ` Vlad Yasevich
2009-02-26 20:01 ` Brian Haley
2009-02-26 20:12 ` Chuck Lever
2009-02-26 20:17 ` Vlad Yasevich
2009-02-26 20:10 ` Vlad Yasevich
2009-02-26 20:20 ` Jay Vosburgh
2009-02-26 20:57 ` Vlad Yasevich
2009-02-26 21:56 ` Jay Vosburgh
2009-02-27 7:25 ` Kyle Moffett
2009-02-27 7:34 ` 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=F613EEFD-2332-4C75-A486-73CDF2BAADDE@oracle.com \
--to=chuck.lever@oracle.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=arvidjaar@mail.ru \
--cc=bonding-devel@lists.sourceforge.net \
--cc=brian.haley@hp.com \
--cc=davem@davemloft.net \
--cc=fubar@us.ibm.com \
--cc=jamagallon@ono.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=tytso@mit.edu \
--cc=vladislav.yasevich@hp.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).