From: Max Reitz <mreitz@redhat.com>
To: David Edmondson <david.edmondson@oracle.com>, qemu-devel@nongnu.org
Cc: "Kevin Wolf" <kwolf@redhat.com>,
"Vladimir Sementsov-Ogievskiy" <vsementsov@virtuozzo.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
qemu-block@nongnu.org
Subject: Re: [PATCH v5] block: report errno when flock fcntl fails
Date: Mon, 18 Jan 2021 17:40:42 +0100 [thread overview]
Message-ID: <28fa9a24-bd2a-4ad8-c731-733e6de9040e@redhat.com> (raw)
In-Reply-To: <20210113164447.2545785-1-david.edmondson@oracle.com>
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.edmondson@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
prev parent reply other threads:[~2021-01-18 17:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-13 16:44 [PATCH v5] block: report errno when flock fcntl fails David Edmondson
2021-01-13 20:45 ` Vladimir Sementsov-Ogievskiy
2021-01-18 16:40 ` Max Reitz [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=28fa9a24-bd2a-4ad8-c731-733e6de9040e@redhat.com \
--to=mreitz@redhat.com \
--cc=david.edmondson@oracle.com \
--cc=f4bug@amsat.org \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@virtuozzo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).