| 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: Sun, 27 Jan 2013 19:13:45 -0800 From: ebiederm@...ssion.com (Eric W. Biederman) To: Cong Wang <amwang@...hat.com> Cc: netdev@...r.kernel.org, "David S. Miller" <davem@...emloft.net> Subject: Re: [Patch net-next] pktgen: use the net namespace of current process instead of init_net Cong Wang <amwang@...hat.com> writes: > On Sun, 2013-01-27 at 18:48 -0800, Eric W. Biederman wrote: >> Cong Wang <amwang@...hat.com> writes: >> >> > From: Cong Wang <amwang@...hat.com> >> > >> > Use the net namespace of the current process loading >> > pktgen module. >> >> Why not add proper support for multiple network namespaces? >> >> It looks like the proc files could be created in each network namespace >> and be controlled from there. > > Hmm, I didn't think much about this. You are right... we could probably > make these proc files per-net. >> Your patch below looks like it could have some unintended effects >> if pktgen was loaded automatically or compiled into the kernel. >> > > In this case, 'current' should be the init process whose net namespace > is init_net, no? If it is a kernel thread that decided to load the module. If it something else who knows. To my knowledge there are no guarantees and I'm not particularly interested in having to worry about current making sense in a module. Eric -- 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
Powered by blists - more mailing lists