[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20071023095208.06c62f59@bree.surriel.com>
Date: Tue, 23 Oct 2007 09:52:08 -0400
From: Rik van Riel <riel@...hat.com>
To: Pavel Emelyanov <xemul@...nvz.org>
Cc: Miklos Szeredi <miklos@...redi.hu>, akpm@...ux-foundation.org,
linux-kernel@...r.kernel.org, xemul@...nvz.org, raven@...maw.net
Subject: Re: futex strangeness in 2.6.23-mm1/UML
On Tue, 23 Oct 2007 12:55:44 +0400
Pavel Emelyanov <xemul@...nvz.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
-
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/
Powered by blists - more mailing lists