mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Cc: William Pitcock <nenolod@dereferenced.org>
Subject: Re: [PATCH] aarch64: signal: fix type definition for ucontext_t.uc_link
Date: Thu, 1 Feb 2018 10:51:06 +0100	[thread overview]
Message-ID: <20180201095105.GN4418@port70.net> (raw)
In-Reply-To: <20180131232924.4051-1-nenolod@dereferenced.org>

* William Pitcock <nenolod@dereferenced.org> [2018-01-31 23:29:24 +0000]:
> When compiling the test program for libucontext, I observed a compiler warning
> concerning assignment to the wrong type (`struct __ucontext` vs `struct ucontext`).
> Accordingly, ucontext_t.uc_link should be the same structure as ucontext_t itself.
> ---
>  arch/aarch64/bits/signal.h | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/arch/aarch64/bits/signal.h b/arch/aarch64/bits/signal.h
> index 5eb3d91f..1c67313d 100644
> --- a/arch/aarch64/bits/signal.h
> +++ b/arch/aarch64/bits/signal.h
> @@ -59,7 +59,7 @@ struct sigaltstack {
>  
>  typedef struct __ucontext {
>  	unsigned long uc_flags;
> -	struct ucontext *uc_link;
> +	struct __ucontext *uc_link;

yes this is a bug (it was introduced because originally
the glibc name was copied for abi compat, then it was
fixed to be namespace clean, but the field was not updated,
meanwhile glibc broke its c++ abi to fix the namespace issue
differently so we will have no abi compat..).

thanks

>  	stack_t uc_stack;
>  	sigset_t uc_sigmask;
>  	mcontext_t uc_mcontext;
> -- 
> 2.16.1


      reply	other threads:[~2018-02-01  9:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-31 23:29 William Pitcock
2018-02-01  9:51 ` Szabolcs Nagy [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=20180201095105.GN4418@port70.net \
    --to=nsz@port70.net \
    --cc=musl@lists.openwall.com \
    --cc=nenolod@dereferenced.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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 NNTP newsgroup(s).