Date: Thu, 16 Sep 2021 12:43:38 +0000 From: bugzilla-noreply@freebsd.org To: python@FreeBSD.org Subject: [Bug 245773] lang/python3: Missing errno.EDEADLOCK Message-ID: <bug-245773-21822-fnLuyuYRIv@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-245773-21822@https.bugs.freebsd.org/bugzilla/> References: <bug-245773-21822@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=3D245773 Willem Jan Withagen <wjw@digiware.nl> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wjw@digiware.nl --- Comment #2 from Willem Jan Withagen <wjw@digiware.nl> --- (In reply to Gleb Popov from comment #1) Yes you are corect. And even on Linux `man 3 errno` tells: ``` EDEADLOCK On most architectures, a synonym for EDEADLK. On some architectures (e.g., Linux MIPS, PowerPC, SPARC), it is a separate error code "File locking deadlock error". ``` and in the errno file itself: ``` asm-generic/errno.h:#define EDEADLK 35 /* Resource deadlock would occur */ asm-generic/errno.h:#define EDEADLOCK EDEADLK ``` But it would be a lot more conveinient if it did exist and worked as expect= ed. The problem of the requestor is not fixed with this, since on FreeBSD `EDEA= DLK` has value 11, so things will not work as expected. And sending error codes between FreeBSD and Linux will require translation = for more than just this one. Then again Python claims that it errno.EDEADLOCK is there, so we should atl= east fix that omission. --=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-245773-21822-fnLuyuYRIv>