public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sergiodj at sergiodj dot net" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/30789] [2.38 Regression] sem_open will fail on multithreaded scenarios when semaphore file doesn't exist (O_CREAT)
Date: Wed, 23 Aug 2023 14:23:12 +0000	[thread overview]
Message-ID: <bug-30789-131-np97gI4ZtA@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30789-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=30789

--- Comment #1 from Sergio Durigan Junior <sergiodj at sergiodj dot net> ---
The bug can be reproduced in Ubuntu Mantic (development version).  Here are the
steps:

As root:

# apt update
# apt install -y mpi-default-bin python3-h5py-mpi

As a regular user:

$ cat > test.py << __EOF__
from h5py import File
from mpi4py import MPI

with File('/tmp/aaaa', 'w', driver='mpio', comm=MPI.COMM_WORLD) as f:
  print(f)
__EOF__
$ mpirun -n 2 python3 test.py

You will notice that the mpirun process hangs indefinitely and consumes 100% of
two CPUs.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  reply	other threads:[~2023-08-23 14:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-23 14:20 [Bug libc/30789] New: " sergiodj at sergiodj dot net
2023-08-23 14:23 ` sergiodj at sergiodj dot net [this message]
2023-08-24 12:38 ` [Bug libc/30789] " sam at gentoo dot org
2023-08-24 12:39 ` sam at gentoo dot org
2023-09-25 14:37 ` freswa at archlinux dot org
2023-11-03 18:46 ` cvs-commit at gcc dot gnu.org
2023-11-03 18:47 ` adhemerval.zanella at linaro dot org
2023-12-03 12:11 ` cvs-commit at gcc dot gnu.org

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=bug-30789-131-np97gI4ZtA@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@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).