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
| ||
|
Date: Thu, 21 Mar 2019 11:50:48 -0400 From: "Michael S. Tsirkin" <mst@...hat.com> To: Stephen Hemminger <stephen@...workplumber.org> Cc: Liran Alon <liran.alon@...cle.com>, Si-Wei Liu <si-wei.liu@...cle.com>, Sridhar Samudrala <sridhar.samudrala@...el.com>, Alexander Duyck <alexander.duyck@...il.com>, Jakub Kicinski <kubakici@...pl>, Jiri Pirko <jiri@...nulli.us>, David Miller <davem@...emloft.net>, Netdev <netdev@...r.kernel.org>, virtualization@...ts.linux-foundation.org, boris.ostrovsky@...cle.com, vijay.balakrishna@...cle.com, jfreimann@...hat.com, ogerlitz@...lanox.com, vuhuong@...lanox.com Subject: Re: [summary] virtio network device failover writeup On Thu, Mar 21, 2019 at 08:45:17AM -0700, Stephen Hemminger wrote: > On Thu, 21 Mar 2019 15:04:37 +0200 > Liran Alon <liran.alon@...cle.com> wrote: > > > > > > > OK. Now what happens if master is moved to another namespace? Do we need > > > to move the slaves too? > > > > No. Why would we move the slaves? The whole point is to make most customer ignore the net-failover slaves and remain them “hidden” in their dedicated netns. > > We won’t prevent customer from explicitly moving the net-failover slaves out of this netns, but we will not move them out of there automatically. > > > The 2-device netvsc already handles case where master changes namespace. Is it by moving slave with it? -- MST
Powered by blists - more mailing lists