public inbox for glibc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Samuel Thibault <sthibaul@sourceware.org>
To: glibc-cvs@sourceware.org
Subject: [glibc] hurd: Add missing sigstate members initialization
Date: Sun, 10 May 2020 23:32:03 +0000 (GMT)	[thread overview]
Message-ID: <20200510233203.7DDCF387086F@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=61416e19218605a54e94edd9740bbe9d2785af6d

commit 61416e19218605a54e94edd9740bbe9d2785af6d
Author: Samuel Thibault <samuel.thibault@ens-lyon.org>
Date:   Mon May 11 01:30:29 2020 +0200

    hurd: Add missing sigstate members initialization
    
    * hurd/hurdsig.c (_hurd_thread_sigstate): Initialize
      critical_section_lock, active_resources, cancel, and cancel_hook fields.

Diff:
---
 hurd/hurdsig.c | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/hurd/hurdsig.c b/hurd/hurdsig.c
index 1e42246ee6..a2741bb7c8 100644
--- a/hurd/hurdsig.c
+++ b/hurd/hurdsig.c
@@ -85,8 +85,9 @@ _hurd_thread_sigstate (thread_t thread)
       ss = malloc (sizeof (*ss));
       if (ss == NULL)
 	__libc_fatal ("hurd: Can't allocate sigstate\n");
-      ss->thread = thread;
+      __spin_lock_init (&ss->critical_section_lock);
       __spin_lock_init (&ss->lock);
+      ss->thread = thread;
 
       /* Initialize default state.  */
       __sigemptyset (&ss->blocked);
@@ -97,6 +98,9 @@ _hurd_thread_sigstate (thread_t thread)
       ss->suspended = MACH_PORT_NULL;
       ss->intr_port = MACH_PORT_NULL;
       ss->context = NULL;
+      ss->active_resources = NULL;
+      ss->cancel = 0;
+      ss->cancel_hook = NULL;
 
       if (thread == MACH_PORT_NULL)
 	{


                 reply	other threads:[~2020-05-10 23:32 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20200510233203.7DDCF387086F@sourceware.org \
    --to=sthibaul@sourceware.org \
    --cc=glibc-cvs@sourceware.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).