On Tue, 23 Oct 2007 09:52:08 -0400 Rik van Riel <[EMAIL PROTECTED]> wrote:
> On Tue, 23 Oct 2007 12:55:44 +0400
> Pavel Emelyanov <[EMAIL PROTECTED]> 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.
argh. Sorry guys, I'd completely forgotten that that bug was present in
-mm1 and I didn't upload the fix into hot-fixes/. Bad me.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
