[Bug 296139] net/openmpi: Fix OMPIO sharedfp/sm crash on FreeBSD due to non-compliant named semaphore string
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Fri, 19 Jun 2026 01:46:42 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=296139
Bug ID: 296139
Summary: net/openmpi: Fix OMPIO sharedfp/sm crash on FreeBSD
due to non-compliant named semaphore string
Product: Ports & Packages
Version: Latest
Hardware: Any
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: Individual Port(s)
Assignee: laurent@FreeBSD.org
Reporter: rikka.goering@outlook.de
Assignee: laurent@FreeBSD.org
Flags: maintainer-feedback?(laurent@FreeBSD.org)
Created attachment 271926
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=271926&action=edit
net/openmpi: Fix OMPIO sharedfp/sm crash on FreeBSD due to non-compliant named
semaphore string
When utilizing OMPIO for parallel I/O operations on local filesystems, OpenMPI
defaults to the shared memory module (sharedfp/sm). Inside
sharedfp_sm_file_open.c, the framework constructs POSIX named semaphores using
the template "OMPIO_%s".
FreeBSD's sem_open(3) strictly enforces the POSIX standard requiring named
semaphores to begin with a leading forward slash ('/'). Because OpenMPI omits
the slash, sem_open fails with EINVAL, causing the entire runtime to abort with
MPI_ERR_OTHER (Error 16).
The attached patch adds the required leading slash ("/OMPIO_%s"), restoring
seamless out-of-the-box parallel I/O functionality (verifiable via standard
suites like Intel MPI Benchmarks).
--
You are receiving this mail because:
You are the assignee for the bug.