From: Vlad Yasevich <vladislav.yasevich@hp.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Brian Haley <brian.haley@hp.com>, Jay Vosburgh <fubar@us.ibm.com>,
David Miller <davem@davemloft.net>,
arvidjaar@mail.ru, 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 15:17:53 -0500 [thread overview]
Message-ID: <49A6F8F1.4060104@hp.com> (raw)
In-Reply-To: <2FBB0F50-8763-4A17-8734-5940FC3FF26A@oracle.com>
Chuck Lever wrote:
> On Feb 26, 2009, at Feb 26, 2009, 3:01 PM, Brian Haley wrote:
>> Chuck Lever wrote:
>>>> 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?
>>
>> No, it should get nothing, and a send should get ENETUNREACH.
>
> Sorry, I got my logic backwards. If IPV6ONLY is intentionally cleared
> on an AF_INET6 socket, it should still be able to handle AF_INET traffic.
Yes. :-)
-vlad
>
> --
> Chuck Lever
> chuck[dot]lever[at]oracle[dot]com
>
next prev parent reply other threads:[~2009-02-26 20:18 UTC|newest]
Thread overview: 20+ 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
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 [this message]
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: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=49A6F8F1.4060104@hp.com \
--to=vladislav.yasevich@hp.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=arvidjaar@mail.ru \
--cc=bonding-devel@lists.sourceforge.net \
--cc=brian.haley@hp.com \
--cc=chuck.lever@oracle.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 \
/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.