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  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Sat, 13 Oct 2007 16:02:30 +0400
From:	Oleg Nesterov <>
To:	Andrew Morton <>
Cc:	Mathieu Desnoyers <>,,,,,, Pavel Emelyanov <>,
	Sukadev Bhattiprolu <>,
	Paul Menage <>,
	"Eric W. Biederman" <>
Subject: Re: 2.6.23-mm1 thread exit_group issue

On 10/13, Oleg Nesterov wrote:
> On 10/12, Andrew Morton wrote:
> >
> > Bisection shows that this problem is caused by these two patches:
> >
> > pid-namespaces-allow-cloning-of-new-namespace.patch
> This?
> Pavel, this patch has a subtle difference compared to what we discussed on
> containers list. It moves put_user(parent_tidptr) from copy_process() to
> do_fork(), so we don't report child's pid if copy_process() failed. I do
> not think this is bad, but Eric seems to disagree with such a change.
> But I can't understand why Andrew sees the same problem _after_ this patch!
> And which patch removed the "put_user(nr, parent_tidptr)" chunk?

Aha. I am looking at

Looks like the original patch was damaged somehow, it doesn't have the
"put_user(nr, parent_tidptr)" code.


To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to
More majordomo info at

Powered by blists - more mailing lists