netdev - Re: [net v3] veth: advertise peer link once both links are tied together

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <1764704950.51133004.1465564858359.JavaMail.zimbra@redhat.com>
Date:	Fri, 10 Jun 2016 09:20:58 -0400 (EDT)
From:	Lance Richardson <lrichard@...hat.com>
To:	nicolas dichtel <nicolas.dichtel@...nd.com>
Cc:	Vincent Bernat <vincent@...nat.im>,
	"David S. Miller" <davem@...emloft.net>,
	Vijay Pandurangan <vijayp@...ayp.ca>,
	Paolo Abeni <pabeni@...hat.com>, netdev@...r.kernel.org
Subject: Re: [net v3] veth: advertise peer link once both links are tied
 together

----- Original Message -----
> From: "Nicolas Dichtel" <nicolas.dichtel@...nd.com>
> To: "Lance Richardson" <lrichard@...hat.com>, "Vincent Bernat" <vincent@...nat.im>
> Cc: "David S. Miller" <davem@...emloft.net>, "Vijay Pandurangan" <vijayp@...ayp.ca>, "Paolo Abeni"
> <pabeni@...hat.com>, netdev@...r.kernel.org
> Sent: Friday, June 10, 2016 9:15:01 AM
> Subject: Re: [net v3] veth: advertise peer link once both links are tied together
> 
> Le 08/06/2016 22:30, Lance Richardson a écrit :
> [snip]
> > I've been pondering how to fix this very problem off-and-on for a few
> > months
> > now, without having arrived at any solution that was particularly
> > satisfying.
> > 
> > The main constraints I've been trying to meet are:
> >    - User-space should be informed of veth pairing for both peers.
> >    - RTM_NEWLINK messages should not refer to interfaces that haven't
> >      been announced to user-space via previous RTM_NEWLINK messages.
> >    - The first (and only the first) RTM_NEWLINK message for a given
> >      interface should have ifi_changes set to ~0U, subsequent RTM_NEWLINK
> >      messages should have ifi_changes set to reflect the flags that
> >      have changed.
> > 
> > This is the closest I've come to a satisfactory solution, it does meet
> > the above constraints but still seems a little unnatural to me:
> The patch looks good to me. Can you submit it formally?
> 

Will post in a bit, thanks!

  Lance