linux-kernel - Re: [PATCH] sched: document wait_for_completion

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20111028084351.GB2010@fieldses.org>
Date:	Fri, 28 Oct 2011 04:43:51 -0400
From:	"J. Bruce Fields" <bfields@...ldses.org>
To:	Ingo Molnar <mingo@...e.hu>, Peter Zijlstra <peterz@...radead.org>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] sched: document wait_for_completion_* return values

On Thu, Oct 06, 2011 at 03:22:46PM -0400, bfields wrote:
> From: J. Bruce Fields <bfields@...hat.com>
> 
> The return-value convention for these functions varies depending on
> whether they're interruptible or can timeout.  It can be a little
> confusing--document it.

Ping?  Should I resend this or send it someplace different?

--b.

> 
> Signed-off-by: J. Bruce Fields <bfields@...hat.com>
> ---
>  kernel/sched.c |   13 +++++++++++++
>  1 files changed, 13 insertions(+), 0 deletions(-)
> 
> diff --git a/kernel/sched.c b/kernel/sched.c
> index ccacdbd..ee84344 100644
> --- a/kernel/sched.c
> +++ b/kernel/sched.c
> @@ -4690,6 +4690,9 @@ EXPORT_SYMBOL(wait_for_completion);
>   * This waits for either a completion of a specific task to be signaled or for a
>   * specified timeout to expire. The timeout is in jiffies. It is not
>   * interruptible.
> + *
> + * The return value is 0 if timed out, and positive (at least 1, or number of
> + * jiffies left till timeout) if completed.
>   */
>  unsigned long __sched
>  wait_for_completion_timeout(struct completion *x, unsigned long timeout)
> @@ -4704,6 +4707,8 @@ EXPORT_SYMBOL(wait_for_completion_timeout);
>   *
>   * This waits for completion of a specific task to be signaled. It is
>   * interruptible.
> + *
> + * The return value is -ERESTARTSYS if interrupted, 0 if completed.
>   */
>  int __sched wait_for_completion_interruptible(struct completion *x)
>  {
> @@ -4721,6 +4726,9 @@ EXPORT_SYMBOL(wait_for_completion_interruptible);
>   *
>   * This waits for either a completion of a specific task to be signaled or for a
>   * specified timeout to expire. It is interruptible. The timeout is in jiffies.
> + *
> + * The return value is -ERESTARTSYS if interrupted, 0 if timed out,
> + * positive (at least 1, or number of jiffies left till timeout) if completed.
>   */
>  long __sched
>  wait_for_completion_interruptible_timeout(struct completion *x,
> @@ -4736,6 +4744,8 @@ EXPORT_SYMBOL(wait_for_completion_interruptible_timeout);
>   *
>   * This waits to be signaled for completion of a specific task. It can be
>   * interrupted by a kill signal.
> + *
> + * The return value is -ERESTARTSYS if interrupted, 0 if completed.
>   */
>  int __sched wait_for_completion_killable(struct completion *x)
>  {
> @@ -4754,6 +4764,9 @@ EXPORT_SYMBOL(wait_for_completion_killable);
>   * This waits for either a completion of a specific task to be
>   * signaled or for a specified timeout to expire. It can be
>   * interrupted by a kill signal. The timeout is in jiffies.
> + *
> + * The return value is -ERESTARTSYS if interrupted, 0 if timed out,
> + * positive (at least 1, or number of jiffies left till timeout) if completed.
>   */
>  long __sched
>  wait_for_completion_killable_timeout(struct completion *x,
> -- 
> 1.7.4.1
> 
--
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/