From: "Sébastien Dugué" <sebastien.dugue@bull.net>
To: Badari Pulavarty <pbadari@gmail.com>
Cc: Christoph Hellwig <hch@infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Suparna Bhattacharya <suparna@in.ibm.com>,
Ulrich Drepper <drepper@redhat.com>,
Zach Brown <zach.brown@oracle.com>, Dave Jones <davej@redhat.com>,
Jean Pierre Dion <jean-pierre.dion@bull.net>,
"linux-aio@kvack.org" <linux-aio@kvack.org>
Subject: Re: [PATCH -mm 3/3][AIO] - AIO completion signal notification
Date: Fri, 10 Nov 2006 10:20:37 +0100 [thread overview]
Message-ID: <1163150437.3879.59.camel@frecb000686> (raw)
In-Reply-To: <1163100428.10295.3.camel@dyn9047017100.beaverton.ibm.com>
On Thu, 2006-11-09 at 11:27 -0800, Badari Pulavarty wrote:
> On Thu, 2006-11-09 at 19:08 +0000, Christoph Hellwig wrote:
>
> Looks much better :)
Indeed ;-)
>
> >
> > static long aio_setup_sigevent(struct kiocb *iocb,
> > struct sigevent __user *user_event)
> > {
> > sigevent_t event;
> > struct task_struct *target;
> > unsigned long flags;
> >
> > if (copy_from_user(&event, user_event, sizeof (event)))
> > return -EFAULT;
> >
> > if (event.sigev_notify == SIGEV_NONE)
> > return 0;
> >
> > iocb->ki_notify.notify = event.sigev_notify;
>
> Don't we want to verify to make sure that we are accepting only
> SIGEV_SIGNAL or SIGEV_THREAD_ID and return -EINVAL, if some
> one passes invalid event ? Like
>
> if ((event.sigev_notify != SIGEV_SIGNAL) &&
> (event.sigev_notify != SIGEV_THREAD_ID))
> return -EINVAL;
That check is done in good_sigevent() below.
>
> > iocb->ki_notify.signo = event.sigev_signo;
> > iocb->ki_notify.value = event.sigev_value;
> >
> > read_lock(&tasklist_lock);
> > target = good_sigevent(&event);
> > if (unlikely(!target || (target->flags & PF_EXITING)))
> > goto out_unlock;
> > iocb->ki_notify.target = target;
> >
> > if (iocb->ki_notify.notify == (SIGEV_SIGNAL|SIGEV_THREAD_ID)) {
> > /*
> > * This reference will be dropped when we're done with
> > * the request.
> > */
> > get_task_struct(target);
> > }
> > read_unlock(&tasklist_lock);
> >
> > /*
> > * NOTE: we cannot free the sigqueue in the completion path as
> > * the signal may not have been delivered to the target task.
> > * Therefore it has to be freed in __sigqueue_free() when the
> > * signal is collected if si_code is SI_ASYNCIO.
> > */
> > iocb->ki_sigq = sigqueue_alloc();
> > if (unlikely(!iocb->ki_sigq)) {
> > put_task_struct(target);
> > return -EAGAIN;
> > }
> >
> > return 0;
> > out_unlock:
> > read_unlock(&tasklist_lock);
> > return -EINVAL;
> > }
Thanks,
Sébastien.
next prev parent reply other threads:[~2006-11-10 9:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-09 15:55 [PATCH -mm 0/3][AIO] - AIO completion signal notification Sébastien Dugué
2006-11-09 15:58 ` [PATCH -mm 1/3][AIO] " Sébastien Dugué
2006-11-09 15:59 ` [PATCH -mm 2/3][AIO] " Sébastien Dugué
2006-11-09 15:59 ` [PATCH -mm 3/3][AIO] " Sébastien Dugué
2006-11-09 18:46 ` Badari Pulavarty
2006-11-10 9:05 ` Sébastien Dugué
2006-11-09 19:08 ` Christoph Hellwig
2006-11-09 19:27 ` Badari Pulavarty
2006-11-10 9:20 ` Sébastien Dugué [this message]
2006-11-10 9:14 ` Sébastien Dugué
2006-11-09 19:18 ` Badari Pulavarty
2006-11-10 9:22 ` Sébastien Dugué
2006-11-10 1:52 ` Badari Pulavarty
2006-11-10 1:54 ` Badari Pulavarty
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=1163150437.3879.59.camel@frecb000686 \
--to=sebastien.dugue@bull.net \
--cc=davej@redhat.com \
--cc=drepper@redhat.com \
--cc=hch@infradead.org \
--cc=jean-pierre.dion@bull.net \
--cc=linux-aio@kvack.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbadari@gmail.com \
--cc=suparna@in.ibm.com \
--cc=zach.brown@oracle.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