On 13.01.21 17:44, David Edmondson wrote:
When a call to fcntl(2) for the purpose of adding file locks fails with an error other than EAGAIN or EACCES, report the error returned by fcntl.EAGAIN or EACCES are elided as they are considered to be common failures, indicating that a conflicting lock is held by another process. No errors are elided when removing file locks. Signed-off-by: David Edmondson <david.edmond...@oracle.com> --- v3: - Remove the now unnecessary updates to the test framework (Max). - Elide the error detail for EAGAIN or EACCES when locking (Kevin, sort-of Max). - Philippe and Vladimir sent Reviewed-by, but things have changed noticeably, so I didn't add them (dme). v4: - Really, really remove the unnecessary updates to the test framework. v5: - Use a macro to avoid duplicating the EAGAIN/EACCES suppression (Vladimir). - Fix "lock" -> "unlock" (Vladimir). - Comment on not eliding errors for the unlock case (Vladimir).
Thanks! I’ve applied this patch to my block branch: https://git.xanclic.moe/XanClic/qemu/commits/branch/block Max
