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: Mon, 23 Jan 2012 07:58:54 +0100 From: Hans Schillstrom <hans.schillstrom@...csson.com> To: "Eric W. Biederman" <ebiederm@...ssion.com> CC: Hagen Paul Pfeifer <hagen@...u.net>, David Miller <davem@...emloft.net>, "equinox@...c24.net" <equinox@...c24.net>, "netdev@...r.kernel.org" <netdev@...r.kernel.org> Subject: Re: RFC Hanging clean-up of a namespace On Monday 23 January 2012 07:25:52 Eric W. Biederman wrote: > Hans Schillstrom <hans.schillstrom@...csson.com> writes: > > > On Friday 20 January 2012 21:55:27 Eric W. Biederman wrote: > >> My current hypothesis is that the namespace actually didn't get freed > >> until the tcp socket finished closing. You can check by looking at when > >> __put_net and then cleanup_net are called. > > > > __put_net() is called just after tcp_write_timer() fires and then > > cleanup_net() > > Hypothesis confirmed. Your speed problem is that it is taking 2 minutes > in the pathological case for your tcp socket to close. > > Do you have any clue why it is taking your sockets so long to close? > Is the other side simply not responding? > The root cause of death is that the other side (init_net namespace) dies first and when it dies all containers will be killed ... /Hans -- 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