From: Markus Armbruster <armbru@redhat.com>
To: Peter Krempa <pkrempa@redhat.com>
Cc: qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>,
Kevin Wolf <kwolf@redhat.com>, Hanna Reitz <hreitz@redhat.com>,
qemu-block@nongnu.org
Subject: Re: [PATCH] block/blkio: Fix inclusion of required headers
Date: Mon, 23 Jan 2023 15:01:37 +0100 [thread overview]
Message-ID: <87h6whbb9a.fsf@pond.sub.org> (raw)
In-Reply-To: <2bc956011404a1ab03342aefde0087b5b4762562.1674477350.git.pkrempa@redhat.com> (Peter Krempa's message of "Mon, 23 Jan 2023 13:39:27 +0100")
Peter Krempa <pkrempa@redhat.com> writes:
> After recent header file inclusion rework the build fails when the blkio
> module is enabled:
>
> ../block/blkio.c: In function ‘blkio_detach_aio_context’:
> ../block/blkio.c:321:24: error: implicit declaration of function ‘bdrv_get_aio_context’; did you mean ‘qemu_get_aio_context’? [-Werror=implicit-function-declaration]
> 321 | aio_set_fd_handler(bdrv_get_aio_context(bs),
> | ^~~~~~~~~~~~~~~~~~~~
> | qemu_get_aio_context
> ../block/blkio.c:321:24: error: nested extern declaration of ‘bdrv_get_aio_context’ [-Werror=nested-externs]
> ../block/blkio.c:321:24: error: passing argument 1 of ‘aio_set_fd_handler’ makes pointer from integer without a cast [-Werror=int-conversion]
> 321 | aio_set_fd_handler(bdrv_get_aio_context(bs),
> | ^~~~~~~~~~~~~~~~~~~~~~~~
> | |
> | int
> In file included from /home/pipo/git/qemu.git/include/qemu/job.h:33,
> from /home/pipo/git/qemu.git/include/block/blockjob.h:30,
> from /home/pipo/git/qemu.git/include/block/block_int-global-state.h:28,
> from /home/pipo/git/qemu.git/include/block/block_int.h:27,
> from ../block/blkio.c:13:
> /home/pipo/git/qemu.git/include/block/aio.h:476:37: note: expected ‘AioContext *’ but argument is of type ‘int’
> 476 | void aio_set_fd_handler(AioContext *ctx,
> | ~~~~~~~~~~~~^~~
> ../block/blkio.c: In function ‘blkio_file_open’:
> ../block/blkio.c:821:34: error: passing argument 2 of ‘blkio_attach_aio_context’ makes pointer from integer without a cast [-Werror=int-conversion]
> 821 | blkio_attach_aio_context(bs, bdrv_get_aio_context(bs));
> | ^~~~~~~~~~~~~~~~~~~~~~~~
> | |
> | int
>
My apologies...
Why are modules disabled by default?
> Fix it by including 'block/block-io.h' which contains the required
> declarations.
>
> Fixes: e2c1c34f139f49ef909bb4322607fb8b39002312
> Signed-off-by: Peter Krempa <pkrempa@redhat.com>
> ---
> block/blkio.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/block/blkio.c b/block/blkio.c
> index 5eae3adfaf..6ad86b23d1 100644
> --- a/block/blkio.c
> +++ b/block/blkio.c
> @@ -19,6 +19,8 @@
> #include "qemu/module.h"
> #include "exec/memory.h" /* for ram_block_discard_disable() */
>
> +#include "block/block-io.h"
> +
> /*
> * Keep the QEMU BlockDriver names identical to the libblkio driver names.
> * Using macros instead of typing out the string literals avoids typos.
Reviewed-by: Markus Armbruster <armbru@redhat.com>
next prev parent reply other threads:[~2023-01-23 14:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-23 12:39 [PATCH] block/blkio: Fix inclusion of required headers Peter Krempa
2023-01-23 14:01 ` Markus Armbruster [this message]
2023-01-23 14:14 ` Peter Krempa
2023-01-23 20:02 ` Stefan Hajnoczi
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=87h6whbb9a.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=hreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=pkrempa@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).