netdev - Re: [PATCH net-next 0/2] ppp: implement x-netns support

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <20150813.212004.553374390201687089.davem@davemloft.net>
Date:	Thu, 13 Aug 2015 21:20:04 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	g.nault@...halink.fr
Cc:	netdev@...r.kernel.org, paulus@...ba.org
Subject: Re: [PATCH net-next 0/2] ppp: implement x-netns support

From: Guillaume Nault <g.nault@...halink.fr>
Date: Thu, 13 Aug 2015 15:28:02 +0200

> This series allows PPP devices to reside in a different netns from the
> PPP unit/channels. Packets only cross netns boundaries when they're
> transmitted between the net_device and the PPP unit (units and channels
> always remain in their creation namespace).
> So only PPP units need to handle cross namespace operations. Channels
> and lower layer protocols aren't affected.
> 
> Patch #1 is a bug fix for an existing namespace deletion bug and has
> been separetly sent to net.
> Patch #2 is the actual x-netns implementation.

Patch #1 needs to be respun with the change I requested.

And this is not the way to submit things that have dependencies
upon bug fixes.

First you submit the bug fix only.  Then you wait for the fix to
propragate from 'net' into 'net-next', and then you can submit
your feature patch which depends upon the fix.

Thank you.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html