From: Oleg Nesterov <oleg@redhat.com>
To: Vitaly Mayatskikh <v.mayatskih@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>, Roland McGrath <roland@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/5] Use copy_wait_opts_to_user() in wait_task_continued()
Date: Mon, 15 Jun 2009 19:13:25 +0200 [thread overview]
Message-ID: <20090615171325.GA8711@redhat.com> (raw)
In-Reply-To: <20090615165536.GC7425@redhat.com>
On 06/15, Oleg Nesterov wrote:
>
> On 05/11, Vitaly Mayatskikh wrote:
> >
> > --- a/kernel/exit.c
> > +++ b/kernel/exit.c
> > @@ -1416,19 +1416,16 @@ static int wait_task_continued(struct wait_opts *wo, struct task_struct *p)
> > get_task_struct(p);
> > read_unlock(&tasklist_lock);
> >
> > - if (!wo->wo_info) {
> > - retval = wo->wo_rusage
> > - ? getrusage(p, RUSAGE_BOTH, wo->wo_rusage) : 0;
> > - put_task_struct(p);
> > - if (!retval && wo->wo_stat)
> > - retval = put_user(0xffff, wo->wo_stat);
> > - if (!retval)
> > - retval = pid;
> > - } else {
> > - retval = wait_noreap_copyout(wo, p, pid, uid,
> > - CLD_CONTINUED, SIGCONT);
> > - BUG_ON(retval == 0);
> > - }
> > + retval = copy_wait_opts_to_user(wo, p, pid, uid,
> > + CLD_CONTINUED, SIGCONT, SIGCHLD);
> > + put_task_struct(p);
> > +
> > + if (!retval && wo->wo_stat)
> > + retval = put_user(0xffff, wo->wo_stat);
>
> This adds another user-visible change. Before the patch, we ignore
> ->wo_stat if ->wo_info != NULL.
Ugh! sorry I was wrong.
->wo_info != NULL means waitid() which sets ->wo_stat = NULL, so this
change is correct.
> I could send the fixes for 3 and 4, but unfortunately Vitaly has
> the vacation now. I think it is better to drop
>
> wait_task_-cleanups-split-wait_noreap_copyout.patch
> wait_task_-cleanups-use-copy_wait_opts_to_user-in-wait_task_stopped.patch
> wait_task_-cleanups-use-copy_wait_opts_to_user-in-do_wait.patch
> wait_task_-cleanups-use-copy_wait_opts_to_user-in-wait_task_zombie.patch
> wait_task_-cleanups-use-copy_wait_opts_to_user-in-wait_task_continued.patch
>
> patches, and wait for Vitaly to redo/resend.
Still I think this would be right :/
Unless Vitaly can see my emails and reply.
Oleg.
next prev parent reply other threads:[~2009-06-15 17:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-11 13:25 [PATCH 0/5] wait_task_* cleanups V2 Vitaly Mayatskikh
2009-05-11 13:25 ` [PATCH 1/5] Split wait_noreap_copyout() Vitaly Mayatskikh
2009-05-11 23:45 ` Andrew Morton
2009-05-20 15:21 ` Vitaly Mayatskikh
2009-05-20 15:57 ` Oleg Nesterov
2009-05-20 20:29 ` Roland McGrath
2009-05-20 18:21 ` Ingo Molnar
2009-05-21 14:12 ` Oleg Nesterov
2009-05-21 14:35 ` Vitaly Mayatskikh
2009-06-09 15:14 ` Vitaly Mayatskikh
2009-05-11 13:25 ` [PATCH 2/5] Use copy_wait_opts_to_user() in wait_task_stopped() Vitaly Mayatskikh
2009-05-11 13:25 ` [PATCH 3/5] Use copy_wait_opts_to_user() in do_wait() Vitaly Mayatskikh
2009-06-15 16:39 ` Oleg Nesterov
2009-05-11 13:25 ` [PATCH 4/5] Use copy_wait_opts_to_user() in wait_task_zombie() Vitaly Mayatskikh
2009-06-15 16:43 ` Oleg Nesterov
2009-05-11 13:25 ` [PATCH 5/5] Use copy_wait_opts_to_user() in wait_task_continued() Vitaly Mayatskikh
2009-06-15 16:55 ` Oleg Nesterov
2009-06-15 17:13 ` Oleg Nesterov [this message]
2009-06-15 17:16 ` Andrew Morton
2009-05-12 3:19 ` [PATCH 0/5] wait_task_* cleanups V2 Roland McGrath
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=20090615171325.GA8711@redhat.com \
--to=oleg@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=roland@redhat.com \
--cc=v.mayatskih@gmail.com \
/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