From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <musl-return-21468-ml=inbox.vuxu.org@lists.openwall.com>
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org
X-Spam-Level: 
X-Spam-Status: No, score=-3.0 required=5.0 tests=HEADER_FROM_DIFFERENT_DOMAINS,
	MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H4,
	RCVD_IN_MSPIKE_WL autolearn=ham autolearn_force=no version=3.4.4
Received: from second.openwall.net (second.openwall.net [193.110.157.125])
	by inbox.vuxu.org (Postfix) with SMTP id 5BDA02EECB
	for <ml@inbox.vuxu.org>; Wed, 23 Oct 2024 02:45:24 +0200 (CEST)
Received: (qmail 28235 invoked by uid 550); 23 Oct 2024 00:45:19 -0000
Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm
Precedence: bulk
List-Post: <mailto:musl@lists.openwall.com>
List-Help: <mailto:musl-help@lists.openwall.com>
List-Unsubscribe: <mailto:musl-unsubscribe@lists.openwall.com>
List-Subscribe: <mailto:musl-subscribe@lists.openwall.com>
List-ID: <musl.lists.openwall.com>
Reply-To: musl@lists.openwall.com
x-ms-reactions: disallow
Received: (qmail 28197 invoked from network); 23 Oct 2024 00:45:19 -0000
Date: Tue, 22 Oct 2024 20:45:11 -0400
From: Rich Felker <dalias@libc.org>
To: Daniele GMail <d.dario76@gmail.com>
Cc: enh <enh@google.com>, musl@lists.openwall.com,
	Daniel Fahlgren <daniel@fahlgren.se>
Message-ID: <20241023004511.GV10433@brightrain.aerifal.cx>
References: <d3a73c323d882e8458e9a9bdce393506a9a05778.camel@gmail.com>
 <20240802140456.GT10433@brightrain.aerifal.cx>
 <CAJgzZor7U1YOUR3BfJcYRfg91oV6WzteVOMZc9d=3oB0VfqddA@mail.gmail.com>
 <CAJgzZoqqqCRZH84MoWsCMpTpso8qAn2Z2PtqoU2W4PXM20SJKQ@mail.gmail.com>
 <c9d4bb3b1bb6e56c57deb1e7dce1d187d26da30a.camel@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <c9d4bb3b1bb6e56c57deb1e7dce1d187d26da30a.camel@gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Subject: Re: [musl] pthread_sigqueue implementation

On Fri, Sep 06, 2024 at 03:58:55PM +0200, Daniele GMail wrote:
> Good day,
> sorry to bother you, I know you have a lot of things boiling and this
> is just another one on the pile.
> 
> But since I didn't see any other mail related to this thread I just
> wanted to know if I can contribute in some way to help.

I'm looking back at the patch from
https://www.openwall.com/lists/musl/2020/02/05/5/1 for possible
inclusion (either in the _np namespace or as-is) and it seems to be
missing the signal blocking pthread_kill has, which is needed to
access the killlock safely. Oddly it still has the "set" local, which
is unused, so it looks like this was intentionally removed..? I think
it should just be added back, and then we should figure out which
name(s) this should be added with..

Rich