Date: Tue, 04 Jul 2023 23:41:49 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 272367] openat(..., O_NONBLOCK | O_EXLOCK) may wrongly return EAGAIN Message-ID: <bug-272367-227-SSLhBbJQxw@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-272367-227@https.bugs.freebsd.org/bugzilla/> References: <bug-272367-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D272367 --- Comment #4 from Alan Somers <asomers@FreeBSD.org> --- (In reply to Konstantin Belousov from comment #2) Your explanation makes sense. But I have a hard time reconciling it with t= his line from flock(2): If a process holding a lock on a file forks and the child explicitly unlocks the file, the parent will lose its lock. That makes it sound like the lock goes away on first close, not on last one= .=20 Or is there a difference between the child closing the file and the child explicitly unlocking the file? --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-272367-227-SSLhBbJQxw>