From: Rik van Riel <riel@redhat.com>
To: Pavel Emelyanov <xemul@openvz.org>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
xemul@openvz.org, raven@themaw.net
Subject: Re: futex strangeness in 2.6.23-mm1/UML
Date: Tue, 23 Oct 2007 09:52:08 -0400 [thread overview]
Message-ID: <20071023095208.06c62f59@bree.surriel.com> (raw)
In-Reply-To: <471DB710.1060603@openvz.org>
On Tue, 23 Oct 2007 12:55:44 +0400
Pavel Emelyanov <xemul@openvz.org> wrote:
> I look at the 2.6.23-mm1 and see that there's one hunk lost. This
> is the one Oleg re-sent some days ago (the mail thread subject was
> 2.6.23-mm1 thread exit_group issue). Here it is (sent 13 oct 2007):
>
> --- kernel/fork.c~ 2007-10-13 15:41:35.000000000 +0400
> +++ kernel/fork.c 2007-10-13 15:41:41.000000000 +0400
> @@ -1443,6 +1443,9 @@ long do_fork(unsigned long clone_flags,
> task_pid_nr_ns(p, current->nsproxy->pid_ns) :
> task_pid_vnr(p);
>
> + if (clone_flags & CLONE_PARENT_SETTID)
> + put_user(nr, parent_tidptr);
> +
> if (clone_flags & CLONE_VFORK) {
> p->vfork_done = &vfork;
> init_completion(&vfork);
>
> Please, try with this patch.
The patch above fixes the issue for me.
Autofs works again as expected.
--
"Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it." - Brian W. Kernighan
next prev parent reply other threads:[~2007-10-23 13:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-22 17:29 futex strangeness in 2.6.23-mm1/UML Miklos Szeredi
2007-10-22 18:53 ` Rik van Riel
2007-10-22 20:48 ` Miklos Szeredi
2007-10-22 21:29 ` Rik van Riel
2007-10-23 0:07 ` Rik van Riel
2007-10-23 0:16 ` Andrew Morton
2007-10-23 1:11 ` Rik van Riel
2007-10-23 1:38 ` Rik van Riel
2007-10-23 2:54 ` Ian Kent
2007-10-23 3:41 ` Jeff Dike
2007-10-23 7:36 ` Miklos Szeredi
2007-10-23 8:55 ` Pavel Emelyanov
2007-10-23 10:23 ` Miklos Szeredi
2007-10-23 13:52 ` Rik van Riel [this message]
2007-10-23 16:00 ` Andrew Morton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071023095208.06c62f59@bree.surriel.com \
--to=riel@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=raven@themaw.net \
--cc=xemul@openvz.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox