public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Siddhesh Poyarekar <siddhesh@sourceware.org>
To: Florian Weimer <fweimer@redhat.com>, libc-alpha@sourceware.org
Cc: Andreas Schwab <schwab@linux-m68k.org>
Subject: Re: [PATCH] Fix use of __pthread_attr_copy in mq_notify (bug 27896)
Date: Wed, 2 Jun 2021 06:51:42 +0530	[thread overview]
Message-ID: <f46c830c-7cc9-4a6b-1f62-f62f8de7dd1e@sourceware.org> (raw)
In-Reply-To: <87wnrd1nor.fsf@oldenburg.str.redhat.com>

On 6/1/21 11:18 PM, Florian Weimer via Libc-alpha wrote:
> __pthread_attr_copy can fail and does not initialize the attribute
> structure in that case.
> 
> If __pthread_attr_copy is never called and there is no allocated
> attribute, pthread_attr_destroy should not be called, otherwise
> there is a null pointer dereference in rt/tst-mqueue6.
> 
> Fixes commit 42d359350510506b87101cf77202fefcbfc790cb
> ("Use __pthread_attr_copy in mq_notify (bug 27896)").
> 
> Tested on i686-linux-gnu and x86_64-linux-gnu.

Thanks, I missed that in my review.  LGTM.

Reviewed-by: Siddhesh Poyarekar <siddhesh@sourceware.org>

> 
> ---
>   sysdeps/unix/sysv/linux/mq_notify.c | 11 +++++++++--
>   1 file changed, 9 insertions(+), 2 deletions(-)
> 
> diff --git a/sysdeps/unix/sysv/linux/mq_notify.c b/sysdeps/unix/sysv/linux/mq_notify.c
> index f7ddfe5a6c..6f46d29d1d 100644
> --- a/sysdeps/unix/sysv/linux/mq_notify.c
> +++ b/sysdeps/unix/sysv/linux/mq_notify.c
> @@ -258,7 +258,14 @@ mq_notify (mqd_t mqdes, const struct sigevent *notification)
>         if (data.attr == NULL)
>   	return -1;
>   
> -      __pthread_attr_copy (data.attr, notification->sigev_notify_attributes);
> +      int ret = __pthread_attr_copy (data.attr,
> +				     notification->sigev_notify_attributes);
> +      if (ret != 0)
> +	{
> +	  free (data.attr);
> +	  __set_errno (ret);
> +	  return -1;
> +	}
>       }
>   
>     /* Construct the new request.  */
> @@ -271,7 +278,7 @@ mq_notify (mqd_t mqdes, const struct sigevent *notification)
>     int retval = INLINE_SYSCALL (mq_notify, 2, mqdes, &se);
>   
>     /* If it failed, free the allocated memory.  */
> -  if (__glibc_unlikely (retval != 0))
> +  if (retval != 0 && data.attr != NULL)
>       {
>         pthread_attr_destroy (data.attr);
>         free (data.attr);
> 


      reply	other threads:[~2021-06-02  1:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-01 17:48 Florian Weimer
2021-06-02  1:21 ` Siddhesh Poyarekar [this message]

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=f46c830c-7cc9-4a6b-1f62-f62f8de7dd1e@sourceware.org \
    --to=siddhesh@sourceware.org \
    --cc=fweimer@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=schwab@linux-m68k.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).