From: Fam Zheng <famz@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: qemu-devel@nongnu.org, kwolf@redhat.com, qemu-stable@nongnu.org,
qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] osdep: Retry SETLK upon EINTR
Date: Thu, 4 Jan 2018 10:19:59 +0800 [thread overview]
Message-ID: <20180104021959.GB23237@lemon.usersys.redhat.com> (raw)
In-Reply-To: <4c7f0e5a-a49c-fc67-7185-5f07cca0f62d@redhat.com>
On Wed, 01/03 16:57, Eric Blake wrote:
> On 12/26/2017 12:53 AM, Fam Zheng wrote:
> > We could hit lock failure if there is a signal that makes fcntl return
> > -1 and errno set to EINTR. In this case we should retry.
>
> Did you hit this in practice? In 'man fcntl' on my Fedora 27 box, the
> DESCRIPTION section only mentions EINTR as possible for F_[OFD_]SETLKW,
> but we don't appear to be using that one (just SETLK and GETLK). On the
> other hand, the ERRORS section of the same document mentions:
>
>
> EINTR cmd is F_SETLKW or F_OFD_SETLKW and the operation was
> inter‐
> rupted by a signal; see signal(7).
>
> EINTR cmd is F_GETLK, F_SETLK, F_OFD_GETLK, or F_OFD_SETLK,
> and the
> operation was interrupted by a signal before the
> lock was
> checked or acquired. Most likely when locking a remote
> file
> (e.g., locking over NFS), but can sometimes happen locally.
>
> (I hate it when information differs between two places in the same
> document, especially if I only read the first place)
Yes, our QE found it when hammering qemu-img convert with SIGUSR1. So both SETLK
and SETLKW can get EINTR.
>
> >
> > Cc: qemu-stable@nongnu.org
> > Signed-off-by: Fam Zheng <famz@redhat.com>
> > ---
> > util/osdep.c | 4 +++-
> > 1 file changed, 3 insertions(+), 1 deletion(-)
> >
> > diff --git a/util/osdep.c b/util/osdep.c
> > index 1231f9f876..a73de0e1ba 100644
> > --- a/util/osdep.c
> > +++ b/util/osdep.c
> > @@ -244,7 +244,9 @@ static int qemu_lock_fcntl(int fd, int64_t start, int64_t len, int fl_type)
> > .l_type = fl_type,
> > };
> > qemu_probe_lock_ops();
> > - ret = fcntl(fd, fcntl_op_setlk, &fl);
> > + do {
> > + ret = fcntl(fd, fcntl_op_setlk, &fl);
> > + } while (ret == -1 && errno == EINTR);
>
> The change makes sense from a maintenance point of view, whether or not
> you hit it in practice.
Thank you for reviewing!
Fam
next prev parent reply other threads:[~2018-01-04 2:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-26 6:53 [Qemu-devel] [PATCH] osdep: Retry SETLK upon EINTR Fam Zheng
2018-01-03 22:57 ` Eric Blake
2018-01-04 2:19 ` Fam Zheng [this message]
2018-01-08 14:45 ` Kevin Wolf
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=20180104021959.GB23237@lemon.usersys.redhat.com \
--to=famz@redhat.com \
--cc=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
/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).