From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sourceware-bugzilla@sourceware.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 1C5C3385E02C; Wed, 23 Aug 2023 14:23:13 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 1C5C3385E02C
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org;
	s=default; t=1692800593;
	bh=Typt8DbZ9FWzRQB0JEBl9Cb/a/6YTCougzErl63c7lA=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=ZA6EbuJ/p1x5uZXzGPWxJcVTEuatK28GbA2fw9TRtqnjLZV/XQEQVasxxlstAiOlC
	 Hem/a+bW7UmyC9m3n4wUtmx9BGMSVQbsASpCLIxu57T7s6rYvTyqinJPZejeTDzb6Y
	 NSwQvTumXZnwsepBdMuC0McJHvZllLTpTz5iKdR4=
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
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: glibc
X-Bugzilla-Component: libc
X-Bugzilla-Version: 2.38
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: sergiodj at sergiodj dot net
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-30789-131-np97gI4ZtA@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-30789-131@http.sourceware.org/bugzilla/>
References: <bug-30789-131@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <glibc-bugs.sourceware.org>

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

--- 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=3D'mpio', comm=3DMPI.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.

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