From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: [musl] bug: sem_close always unmaps semaphore regardless of ref count
Date: Wed, 28 Oct 2020 16:11:05 -0400 [thread overview]
Message-ID: <20201028201104.GH534@brightrain.aerifal.cx> (raw)
[-- Attachment #1: Type: text/plain, Size: 198 bytes --]
I found this while reading the code during review of lock usage for
MT-fork. Test case attached (can be adapted for libc-test regression
tests, I think, or improved to be a conformance test).
Rich
[-- Attachment #2: sem_close.c --]
[-- Type: text/plain, Size: 218 bytes --]
#include <semaphore.h>
int main()
{
char buf[] = "mysemXXXXXX";
if (!mktemp(buf)) return 1;
sem_t *sem = sem_open(buf, O_CREAT|O_EXCL, 0600);
sem_open(buf, 0);
sem_unlink(buf);
sem_close(sem);
sem_post(sem);
}
next reply other threads:[~2020-10-28 20:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-28 20:11 Rich Felker [this message]
2020-10-28 20:18 ` Rich Felker
2020-10-28 22:01 ` Szabolcs Nagy
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=20201028201104.GH534@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=musl@lists.openwall.com \
/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).