linux-kernel - Re: [PATCH] pidns: Fix wait for zombies to be reaped in zap_pid_ns

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 30 Oct 2010 00:07:33 -0700
From:	Sukadev Bhattiprolu <sukadev@...ux.vnet.ibm.com>
To:	"Eric W. Biederman" <ebiederm@...ssion.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Linux Containers <containers@...ts.osdl.org>,
	linux-kernel@...r.kernel.org, Oleg Nesterov <oleg@...hat.com>,
	Pavel Emelyanov <xemul@...nvz.org>
Subject: Re: [PATCH] pidns: Fix wait for zombies to be reaped in
	zap_pid_ns_processes

Eric W. Biederman [ebiederm@...ssion.com] wrote:
| Louis Rilling <Louis.Rilling@...labs.com> writes:
| 
| > This patch looks like it is working (only a small RCU issue shown below). I
| > couldn't try it yet though.
| 
| It certainly worked in my testing. 
| 
| > I must admit that I am using a similar back-off solution in Kerrighed (not to
| > solve the issue of proc_flush_task(), but for one of the reasons that you stated
| > above: we want to be sure that all tasks of the namespace have been reaped), but
| > I considered it too ugly to propose it for Linux ;)
| 
| Well sometimes you have to go with what works.
| 
| Thanks for spotting those issue with my patch.  I guess it needs one more
| pass before I can call it done.

Eric,

Do you plan to resend this patch ? 

FYI, we ran into the problem that Louis Rilling reported when testing with
the checkpoint/restart code and this patch fixes the problem (after a minor
tweak to the C/R code).

Thanks,

Sukadev
--
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/