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  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]
Date:   Tue, 14 Nov 2017 10:53:51 -0800
From:   Cong Wang <>
To:     Jiri Pirko <>
Cc:     Linux Kernel Network Developers <>,
        David Miller <>,
        Jamal Hadi Salim <>,,
        Ido Schimmel <>,
        Eric Dumazet <>,
        Willem de Bruijn <>,
        tcharding <>,
        John Fastabend <>,
        Jakub Kicinski <>,
        Daniel Borkmann <>
Subject: Re: [patch net] net: forbid netdev used by mirred tc act from being
 moved to another netns

On Mon, Nov 13, 2017 at 10:35 PM, Jiri Pirko <> wrote:
> Okay. What about my question? Should we allow adding an action mirred
> pointing to a netdev in another netns? I think it would make sense in
> case we consider movement of mirred device legit.

I don't think it is possible to add an action pointing to any netdev in
other netns in current code base, you just can't find it.

Moving a netdev after linking it to an action is different, if you want to
argue this using above question. Because we allow other "linking"
netdev to be moved too, like a tunnel device on top of a physical
one (this is why we have netnsid).

The "linking" of a mirred action might not be as strong as a tunnel
device "linking", but the idea is pretty much similar, I don't see
anything fundamentally wrong.

Powered by blists - more mailing lists