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  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:   Mon, 27 Jan 2020 11:04:01 +0100 (CET)
From:   David Miller <davem@...emloft.net>
To:     jiri@...nulli.us
Cc:     netdev@...r.kernel.org, jakub.kicinski@...ronome.com,
        saeedm@...lanox.com, leon@...nel.org, tariqt@...lanox.com,
        ayal@...lanox.com, vladbu@...lanox.com, michaelgur@...lanox.com,
        moshe@...lanox.com, mlxsw@...lanox.com, dsahern@...il.com
Subject: Re: [patch net-next v2 0/4] net: allow per-net notifier to follow
 netdev into namespace

From: Jiri Pirko <jiri@...nulli.us>
Date: Sat, 25 Jan 2020 12:17:05 +0100

> From: Jiri Pirko <jiri@...lanox.com>
> 
> Currently we have per-net notifier, which allows to get only
> notifications relevant to particular network namespace. That is enough
> for drivers that have netdevs local in a particular namespace (cannot
> move elsewhere).
> 
> However if netdev can change namespace, per-net notifier cannot be used.
> Introduce dev_net variant that is basically per-net notifier with an
> extension that re-registers the per-net notifier upon netdev namespace
> change. Basically the per-net notifier follows the netdev into
> namespace.

Series applied, thanks Jiri.

Powered by blists - more mailing lists