From: Kevin Wolf <kwolf@redhat.com>
To: Feng Li <lifeng1519@gmail.com>
Cc: Kyle Zhang <kyle@smartx.com>, Li Feng <fengli@smartx.com>,
"open list:All patches CC here" <qemu-devel@nongnu.org>,
"open list:raw" <qemu-block@nongnu.org>,
Max Reitz <mreitz@redhat.com>
Subject: Re: [PATCH] file-posix: check the use_lock
Date: Mon, 7 Dec 2020 12:17:02 +0100 [thread overview]
Message-ID: <20201207111702.GA5281@merkur.fritz.box> (raw)
In-Reply-To: <CAEK8JBAu0jStwRgD=_hNDn1cHzxPXZyvHmikUtKcriCNvHxDKA@mail.gmail.com>
Am 07.12.2020 um 11:50 hat Feng Li geschrieben:
> Hi Kevin,
>
> I have read the 182 test, and I'm very confused about the test.
> I'm not familiar with the permissions and locks in the qemu.
> Could you give me more tips about how to complete the test?
Hm, actually, to produce a failure, we would have to have a filesystem
in the host that doesn't support locks. I don't even know how to get
such a filesystem manually, and it's probably completely impossible in a
test case without root permissions.
So maybe just add a more detailed description of the bug to the commit
message, and we'll have to apply it without a test.
Kevin
> Li Feng <fengli@smartx.com> 于2020年12月4日周五 下午6:55写道:
> >
> > Hi Kevin,
> > Thanks for your reply.
> >
> > In my scenario, my NFS server doesn't support the file lock.
> > And when I set the file.locking = false, the Qemu still reports:
> > qemu-system-x86_64: -drive
> > file=/tmp/nfs/a,format=raw,cache=none,aio=native,if=none,id=drive-virtio-disk1,file.locking=on:
> > Failed to lock byte 100
> >
> > I will look at the iotest 182 and try to add a test.
> >
> > Thanks,
> > Feng Li
> >
> > Kevin Wolf <kwolf@redhat.com> 于2020年12月4日周五 下午6:40写道:
> > >
> > > Am 04.12.2020 um 11:28 hat Li Feng geschrieben:
> > > > When setting the file.locking = false, we shouldn't set the lock.
> > > >
> > > > Signed-off-by: Li Feng <fengli@smartx.com>
> > >
> > > This looks right to me, but can you add a test for this scenario to
> > > iotest 182? This would both demonstrate the effect of the bug (I think
> > > it would be that files are locked after reopen even with locking=off?)
> > > and make sure that we won't have a regression later. Mentioning the
> > > effect in the commit message would be good, too.
> > >
> > > Kevin
> > >
> > > > block/file-posix.c | 2 +-
> > > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > > >
> > > > diff --git a/block/file-posix.c b/block/file-posix.c
> > > > index d5fd1dbcd2..806764f7e3 100644
> > > > --- a/block/file-posix.c
> > > > +++ b/block/file-posix.c
> > > > @@ -3104,7 +3104,7 @@ static int raw_check_perm(BlockDriverState *bs, uint64_t perm, uint64_t shared,
> > > > }
> > > >
> > > > /* Copy locks to the new fd */
> > > > - if (s->perm_change_fd) {
> > > > + if (s->perm_change_fd && s->use_lock) {
> > > > ret = raw_apply_lock_bytes(NULL, s->perm_change_fd, perm, ~shared,
> > > > false, errp);
> > > > if (ret < 0) {
> > > > --
> > > > 2.24.3
> > > >
> > >
>
next prev parent reply other threads:[~2020-12-07 11:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-04 10:28 [PATCH] file-posix: check the use_lock Li Feng
2020-12-04 10:40 ` Kevin Wolf
2020-12-04 10:55 ` Li Feng
2020-12-07 10:50 ` Feng Li
2020-12-07 11:17 ` Kevin Wolf [this message]
2020-12-07 11:29 ` Li Feng
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=20201207111702.GA5281@merkur.fritz.box \
--to=kwolf@redhat.com \
--cc=fengli@smartx.com \
--cc=kyle@smartx.com \
--cc=lifeng1519@gmail.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@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).