From: David Miller <davem@davemloft.net>
To: sd@queasysnail.net
Cc: dsahern@gmail.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next] ipv6: allow userspace to add IFA_F_OPTIMISTIC addresses
Date: Mon, 26 Feb 2018 12:11:27 -0500 (EST) [thread overview]
Message-ID: <20180226.121127.2237252602192340288.davem@davemloft.net> (raw)
In-Reply-To: <20180226165619.GA10603@bistromath.localdomain>
From: Sabrina Dubroca <sd@queasysnail.net>
Date: Mon, 26 Feb 2018 17:56:19 +0100
> 2018-02-26, 10:57:11 -0500, David Miller wrote:
>> Userland is now repsonsible for implementing correct behavior when it
>> takes over this task, and therefore the kernel has no say in the
>> matter of proper ipv6 neighbor discovery and addrconf behavior.
>
> As an aside, that's also the case whenever userland uses packet
> sockets.
When you use packet sockets, all bets are off and it is clearly the
case that the user gets to keep the broken pieces when things go
wrong.
That's completely different to this case, which is a bonfide explicit
allowance for userspace to take over these fundamental protocol tasks
from the kernel.
So please do not use packet sockets as an example of a similar
situation.
next prev parent reply other threads:[~2018-02-26 17:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-20 16:43 [PATCH net-next] ipv6: allow userspace to add IFA_F_OPTIMISTIC addresses Sabrina Dubroca
2018-02-20 17:25 ` David Ahern
2018-02-20 18:17 ` Sabrina Dubroca
2018-02-21 20:34 ` David Miller
2018-02-26 15:41 ` Sabrina Dubroca
2018-02-26 15:57 ` David Miller
2018-02-26 16:56 ` Sabrina Dubroca
2018-02-26 17:11 ` David Miller [this message]
2018-02-27 14:13 ` Sabrina Dubroca
2018-02-27 15:47 ` David Miller
2018-02-27 23:22 ` Sabrina Dubroca
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=20180226.121127.2237252602192340288.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=sd@queasysnail.net \
/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).