From: Eric Blake <eblake@redhat.com>
To: Dimitris Aragiorgis <dimara@arrikto.com>, qemu-devel@nongnu.org
Cc: kwolf@redhat.com, pbonzini@redhat.com, stefanha@redhat.com,
qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v3 3/5] raw-posix: DPRINTF instead of DEBUG_BLOCK_PRINT
Date: Thu, 14 May 2015 08:05:19 -0600 [thread overview]
Message-ID: <5554AB9F.8020008@redhat.com> (raw)
In-Reply-To: <1431601275-4586-4-git-send-email-dimara@arrikto.com>
[-- Attachment #1: Type: text/plain, Size: 1885 bytes --]
On 05/14/2015 05:01 AM, Dimitris Aragiorgis wrote:
> Building the QEMU tools fails if we #define DEBUG_BLOCK inside
> block/raw-posix.c. Here instead of adding qemu-log.o in block-obj-y
> so that DEBUG_BLOCK_PRINT can be used, we substitute the latter with
> a simple DPRINTF() (that does not cause bit-rot).
>
> Signed-off-by: Dimitris Aragiorgis <dimara@arrikto.com>
> ---
> block/raw-posix.c | 17 +++++++++++------
> 1 file changed, 11 insertions(+), 6 deletions(-)
>
> +#define DPRINTF(fmt, ...) \
> +do { \
> + if (DEBUG_BLOCK_PRINT) \
> + printf(fmt, ## __VA_ARGS__); \
> +} while (0)
Still missing {} for the if statement.
[It might be nice to update scripts/checkpatch.pl to catch correct {}
inside macros, but that's a project for a different day.]
> @@ -1023,7 +1028,7 @@ static int xfs_write_zeroes(BDRVRawState *s, int64_t offset, uint64_t bytes)
> fl.l_len = bytes;
>
> if (xfsctl(NULL, s->fd, XFS_IOC_ZERO_RANGE, &fl) < 0) {
> - DEBUG_BLOCK_PRINT("cannot write zero range (%s)\n", strerror(errno));
> + DPRINTF("cannot write zero range (%s)\n", strerror(errno));
> return -errno;
> }
Pre-existing bug - strerror() and/or DPRINTF() can clobber errno, so
your return value may be destroyed. You'll have to save errno into a
temporary variable prior to DPRINTF, and return that value.
>
> @@ -1040,7 +1045,7 @@ static int xfs_discard(BDRVRawState *s, int64_t offset, uint64_t bytes)
> fl.l_len = bytes;
>
> if (xfsctl(NULL, s->fd, XFS_IOC_UNRESVSP64, &fl) < 0) {
> - DEBUG_BLOCK_PRINT("cannot punch hole (%s)\n", strerror(errno));
> + DPRINTF("cannot punch hole (%s)\n", strerror(errno));
> return -errno;
Here too.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2015-05-14 14:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-14 11:01 [Qemu-devel] [PATCH v3 0/5] Some fixes related to scsi-generic Dimitris Aragiorgis
2015-05-14 11:01 ` [Qemu-devel] [PATCH v3 1/5] block: Use bdrv_is_sg() everywhere Dimitris Aragiorgis
2015-05-14 11:01 ` [Qemu-devel] [PATCH v3 2/5] Fix migration in case of scsi-generic Dimitris Aragiorgis
2015-05-14 11:01 ` [Qemu-devel] [PATCH v3 3/5] raw-posix: DPRINTF instead of DEBUG_BLOCK_PRINT Dimitris Aragiorgis
2015-05-14 14:05 ` Eric Blake [this message]
2015-05-14 11:01 ` [Qemu-devel] [PATCH v3 4/5] raw-posix: Use DPRINTF for DEBUG_FLOPPY Dimitris Aragiorgis
2015-05-14 11:01 ` [Qemu-devel] [PATCH v3 5/5] raw-posix: Introduce hdev_is_sg() Dimitris Aragiorgis
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=5554AB9F.8020008@redhat.com \
--to=eblake@redhat.com \
--cc=dimara@arrikto.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).