From: Niels de Vos <ndevos@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: qemu-block@nongnu.org, integration@gluster.org,
Prasanna Kumar Kalever <prasanna.kalever@redhat.com>,
qemu-devel@nongnu.org, Cole Robinson <crobinso@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 1/2] block/gluster: Handle changed glfs_ftruncate signature
Date: Tue, 5 Mar 2019 16:16:57 +0100 [thread overview]
Message-ID: <20190305151657.GC16424@ndevos-x270> (raw)
In-Reply-To: <20190304164144.GR4239@redhat.com>
On Mon, Mar 04, 2019 at 04:41:44PM +0000, Daniel P. Berrangé wrote:
> On Mon, Mar 04, 2019 at 05:21:02PM +0100, Niels de Vos wrote:
> > From: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
> >
> > New versions of Glusters libgfapi.so have an updated glfs_ftruncate()
> > function that returns additional 'struct stat' structures to enable
> > advanced caching of attributes. This is useful for file servers, not so
> > much for QEMU. Nevertheless, the API has changed and needs to be
> > adopted.
> >
> > Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
> > Signed-off-by: Niels de Vos <ndevos@redhat.com>
> >
> > ---
> > v4: rebase to current master branch
> > v3: define old backwards compatible glfs_ftruncate() macro, from Eric Blake
> > v2: do a compile check as suggested by Eric Blake
> > ---
> > block/gluster.c | 11 +++++++++--
> > configure | 18 ++++++++++++++++++
> > 2 files changed, 27 insertions(+), 2 deletions(-)
> >
> > diff --git a/block/gluster.c b/block/gluster.c
> > index af64330211..86e5278524 100644
> > --- a/block/gluster.c
> > +++ b/block/gluster.c
> > @@ -20,6 +20,10 @@
> > #include "qemu/option.h"
> > #include "qemu/cutils.h"
> >
> > +#ifdef CONFIG_GLUSTERFS_LEGACY_FTRUNCATE
> > +# define glfs_ftruncate(fd, offset, _u1, _u2) glfs_ftruncate(fd, offset)
> > +#endif
>
> I don't much like this approach as it sets up a trapdoor. If future
> QEMU passes a non-NULL value for the 3rd/4th argument it will be
> silently ignored depending on glfs version built against which can
> result in incorrect behaviour at runtime. If we reverse it:
>
> #ifndef CONFIG_GLUSTERFS_LEGACY_FTRUNCATE
> # define glfs_ftruncate(fd, offset) glfs_ftruncate(fd, offset, NULL, NULL)
> #endif
>
> then it ensures we can't silently do the wrong thing in future. Anyone
> who wants to use the 3rd/4th args will have to make an explicit effort
> to ensure it works correctly with old glfs APIs. An added benefit is
> that it avoids the following patch chunks.
Thanks for the suggestion. All makes sense and I'll update the patch
accordingly.
Niels
next prev parent reply other threads:[~2019-03-05 15:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-04 16:21 [Qemu-devel] [PATCH 0/2] block: Gluster 6 compatibility Niels de Vos
2019-03-04 16:21 ` [Qemu-devel] [PATCH 1/2] block/gluster: Handle changed glfs_ftruncate signature Niels de Vos
2019-03-04 16:41 ` Daniel P. Berrangé
2019-03-05 15:16 ` Niels de Vos [this message]
2019-03-04 16:21 ` [Qemu-devel] [PATCH 2/2] gluster: the glfs_io_cbk callback function pointer adds pre/post stat args Niels de Vos
2019-03-05 10:29 ` [Qemu-devel] [Qemu-block] " Kevin Wolf
2019-03-05 15:18 ` Niels de Vos
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=20190305151657.GC16424@ndevos-x270 \
--to=ndevos@redhat.com \
--cc=berrange@redhat.com \
--cc=crobinso@redhat.com \
--cc=integration@gluster.org \
--cc=prasanna.kalever@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).