From: Hans-Werner Hilse <hwhilse@gmail.com>
To: User-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] [PATCH v2 1/3] um: Do not use __ptr_t type for stack_t's .ss pointer
Date: Thu, 11 Jun 2015 11:29:18 +0200 [thread overview]
Message-ID: <1434014960-14774-2-git-send-email-hwhilse@gmail.com> (raw)
In-Reply-To: <1434014960-14774-1-git-send-email-hwhilse@gmail.com>
__ptr_t type is a glibc-specific type, while the generally
documented type is a void*. That's what other C libraries use,
too.
Signed-off-by: Hans-Werner Hilse <hwhilse@gmail.com>
---
arch/um/os-Linux/signal.c | 8 +++++---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/arch/um/os-Linux/signal.c b/arch/um/os-Linux/signal.c
index 7b605e4..036d0db 100644
--- a/arch/um/os-Linux/signal.c
+++ b/arch/um/os-Linux/signal.c
@@ -112,9 +112,11 @@ void timer_init(void)
void set_sigstack(void *sig_stack, int size)
{
- stack_t stack = ((stack_t) { .ss_flags = 0,
- .ss_sp = (__ptr_t) sig_stack,
- .ss_size = size - sizeof(void *) });
+ stack_t stack = {
+ .ss_flags = 0,
+ .ss_sp = sig_stack,
+ .ss_size = size - sizeof(void *)
+ };
if (sigaltstack(&stack, NULL) != 0)
panic("enabling signal stack failed, errno = %d\n", errno);
--
2.4.2
------------------------------------------------------------------------------
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2015-06-11 9:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-11 9:29 [uml-devel] [PATCH v2 0/3] musl compatibility patches Hans-Werner Hilse
2015-06-11 9:29 ` Hans-Werner Hilse [this message]
2015-06-11 9:29 ` [uml-devel] [PATCH v2 2/3] um: Do not use stdin and stdout identifiers for struct members Hans-Werner Hilse
2015-06-11 9:29 ` [uml-devel] [PATCH v2 3/3] um: Include sys/types.h for makedev(), major(), minor() Hans-Werner Hilse
2015-06-25 20:42 ` [uml-devel] [PATCH v2 0/3] musl compatibility patches Richard Weinberger
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=1434014960-14774-2-git-send-email-hwhilse@gmail.com \
--to=hwhilse@gmail.com \
--cc=User-mode-linux-devel@lists.sourceforge.net \
/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