From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Fiona Ebner <f.ebner@proxmox.com>, qemu-devel@nongnu.org
Cc: qemu-block@nongnu.org, qemu-stable@nongnu.org, hreitz@redhat.com,
kwolf@redhat.com, vsementsov@yandex-team.ru, jsnow@redhat.com,
f.weber@proxmox.com
Subject: Re: [PATCH] block/copy-before-write: use uint64_t for timeout in nanoseconds
Date: Mon, 29 Apr 2024 16:36:57 +0200 [thread overview]
Message-ID: <befd2718-526e-4407-8620-476dfa290c48@linaro.org> (raw)
In-Reply-To: <20240429141934.442154-1-f.ebner@proxmox.com>
Hi Fiona,
On 29/4/24 16:19, Fiona Ebner wrote:
Not everybody uses an email client that shows the patch content just
after the subject (your first lines wasn't making sense at first).
Simply duplicating the subject helps to understand:
Use uint64_t for timeout in nanoseconds ...
> rather than the uint32_t for which the maximum is slightly more than 4
> seconds and larger values would overflow. The QAPI interface allows
> specifying the number of seconds, so only values 0 to 4 are safe right
> now, other values lead to a much lower timeout than a user expects.
>
> The block_copy() call where this is used already takes a uint64_t for
> the timeout, so no change required there.
>
> Fixes: 6db7fd1ca9 ("block/copy-before-write: implement cbw-timeout option")
> Reported-by: Friedrich Weber <f.weber@proxmox.com>
> Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
> ---
> block/copy-before-write.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/block/copy-before-write.c b/block/copy-before-write.c
> index 8aba27a71d..026fa9840f 100644
> --- a/block/copy-before-write.c
> +++ b/block/copy-before-write.c
> @@ -43,7 +43,7 @@ typedef struct BDRVCopyBeforeWriteState {
> BlockCopyState *bcs;
> BdrvChild *target;
> OnCbwError on_cbw_error;
> - uint32_t cbw_timeout_ns;
> + uint64_t cbw_timeout_ns;
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
next prev parent reply other threads:[~2024-04-29 14:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-29 14:19 [PATCH] block/copy-before-write: use uint64_t for timeout in nanoseconds Fiona Ebner
2024-04-29 14:36 ` Philippe Mathieu-Daudé [this message]
2024-04-29 14:46 ` Fiona Ebner
2024-04-29 14:52 ` Vladimir Sementsov-Ogievskiy
2024-05-28 16:06 ` Kevin Wolf
2024-06-03 14:45 ` Fiona Ebner
2024-06-03 16:09 ` Kevin Wolf
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=befd2718-526e-4407-8620-476dfa290c48@linaro.org \
--to=philmd@linaro.org \
--cc=f.ebner@proxmox.com \
--cc=f.weber@proxmox.com \
--cc=hreitz@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=vsementsov@yandex-team.ru \
/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).