| 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: Tue, 10 Jul 2012 10:36:12 -0700 From: Jay Vosburgh <fubar@...ibm.com> To: David Miller <davem@...emloft.net> cc: ebiederm@...ssion.com, dilip.daya@...com, linux-kernel@...r.kernel.org, containers@...ts.linux-foundation.org, netdev@...r.kernel.org, serge@...lyn.com Subject: Re: [PATCH 2/2] bonding: debugfs and network namespaces are incompatible David Miller <davem@...emloft.net> wrote: >From: ebiederm@...ssion.com (Eric W. Biederman) >Date: Mon, 09 Jul 2012 13:52:43 -0700 > >> >> The bonding debugfs support has been broken in the presence of network >> namespaces since it has been added. The debugfs support does not handle >> multiple bonding devices with the same name in different network >> namespaces. >> >> I haven't had any bug reports, and I'm not interested in getting any. >> Disable the debugfs support when network namespaces are enabled. >> >> Signed-off-by: "Eric W. Biederman" <ebiederm@...ssion.com> > >Applied. Since distro kernels appear to set CONFIG_NET_NS, doesn't this effectively disable debugfs for bonding on most distros? Do the other network device drivers that support debugfs have a similar problem? E.g., if each of two namespaces have an skge device with the same name, will there be a debugfs conflict there as well? -J --- -Jay Vosburgh, IBM Linux Technology Center, fubar@...ibm.com -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists