From: "Daniel P. Berrange" <berrange@redhat.com>
To: Felipe Franciosi <felipe@nutanix.com>
Cc: marcandre.lureau@redhat.com, pbonzini@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2 1/3] io: Fix double shift usages on QIOChannel features
Date: Wed, 28 Sep 2016 13:44:00 +0100 [thread overview]
Message-ID: <20160928124400.GB15510@redhat.com> (raw)
In-Reply-To: <1475066167-17635-2-git-send-email-felipe@nutanix.com>
On Wed, Sep 28, 2016 at 05:36:05AM -0700, Felipe Franciosi wrote:
> When QIOChannels were introduced in 666a3af9, the feature bits were
> already defined shifted. However, when using them, the code was shifting
> them again. The incorrect use was consistent until 74b6ce43, where
> QIO_CHANNEL_FEATURE_LISTEN was defined shifted but tested unshifted.
>
> This patch changes the definition to be unshifted and fixes the
> incorrect usage introduced on 74b6ce43.
>
> Signed-off-by: Felipe Franciosi <felipe@nutanix.com>
> ---
> include/io/channel.h | 6 +++---
> io/channel-socket.c | 2 +-
> 2 files changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/include/io/channel.h b/include/io/channel.h
> index 752e89f..5368604 100644
> --- a/include/io/channel.h
> +++ b/include/io/channel.h
> @@ -40,9 +40,9 @@ typedef struct QIOChannelClass QIOChannelClass;
> typedef enum QIOChannelFeature QIOChannelFeature;
>
> enum QIOChannelFeature {
> - QIO_CHANNEL_FEATURE_FD_PASS = (1 << 0),
> - QIO_CHANNEL_FEATURE_SHUTDOWN = (1 << 1),
> - QIO_CHANNEL_FEATURE_LISTEN = (1 << 2),
> + QIO_CHANNEL_FEATURE_FD_PASS,
> + QIO_CHANNEL_FEATURE_SHUTDOWN,
> + QIO_CHANNEL_FEATURE_LISTEN,
> };
>
>
> diff --git a/io/channel-socket.c b/io/channel-socket.c
> index 196a4f1..6710b2e 100644
> --- a/io/channel-socket.c
> +++ b/io/channel-socket.c
> @@ -403,7 +403,7 @@ static void qio_channel_socket_finalize(Object *obj)
> QIOChannelSocket *ioc = QIO_CHANNEL_SOCKET(obj);
>
> if (ioc->fd != -1) {
> - if (QIO_CHANNEL(ioc)->features & QIO_CHANNEL_FEATURE_LISTEN) {
> + if (QIO_CHANNEL(ioc)->features & (1 << QIO_CHANNEL_FEATURE_LISTEN)) {
> Error *err = NULL;
>
> socket_listen_cleanup(ioc->fd, &err);
The change looks good, but this patch is missing additions to the
various tests/test-io-channel-*.c files, to validate that we correctly
report the SHUTDOWN/LISTEN features being set.
Any test addition should fail on current git master, and succeed with
this fix applied.
Regards,
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://entangle-photo.org -o- http://search.cpan.org/~danberr/ :|
next prev parent reply other threads:[~2016-09-28 12:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-28 12:36 [Qemu-devel] [PATCH v2 0/3] io: Various fixes around QIOChannel Features Felipe Franciosi
2016-09-28 12:36 ` [Qemu-devel] [PATCH v2 1/3] io: Fix double shift usages on QIOChannel features Felipe Franciosi
2016-09-28 12:44 ` Daniel P. Berrange [this message]
2016-09-28 14:49 ` Felipe Franciosi
2016-09-28 15:00 ` Daniel P. Berrange
2016-09-28 12:36 ` [Qemu-devel] [PATCH v2 2/3] io: Use qio_channel_has_feature() where applicable Felipe Franciosi
2016-09-28 12:36 ` [Qemu-devel] [PATCH v2 3/3] io: Introduce a qio_channel_set_feature() helper Felipe Franciosi
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=20160928124400.GB15510@redhat.com \
--to=berrange@redhat.com \
--cc=felipe@nutanix.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.