From: Anthony PERARD <anthony@xenproject.org>
To: Liam Merwick <liam.merwick@oracle.com>
Cc: dwmw@amazon.co.uk, roger.pau@citrix.com,
xen-devel@lists.xenproject.org, qemu-devel@nongnu.org
Subject: Re: [PATCH] hw/xen: Fix trace_xs_node_read() params
Date: Mon, 26 May 2025 18:19:06 +0200 [thread overview]
Message-ID: <aDSUesF-KUYnIoxM@l14> (raw)
In-Reply-To: <20250523160134.218997-1-liam.merwick@oracle.com>
On Fri, May 23, 2025 at 04:01:34PM +0000, Liam Merwick wrote:
> When the '--enable-trace-backends=syslog' build option is configured,
> the following compilation error is encountered.
>
> In file included from /usr/include/sys/syslog.h:207,
> from /usr/include/syslog.h:1,
> from ./trace/trace-hw_xen.h:224,
> from ../hw/xen/trace.h:1,
> from ../hw/xen/xen-bus-helper.c:13:
> In function ‘syslog’,
> inlined from ‘_nocheck__trace_xs_node_read’ at ../hw/xen/trace-events:41:9,
> inlined from ‘trace_xs_node_read’ at trace/trace-hw_xen.h:903:9,
> inlined from ‘xs_node_read’ at ../hw/xen/xen-bus-helper.c:154:5:
> /usr/include/bits/syslog.h:45:3: error: ‘%s’ directive argument is null [-Werror=format-overflow=]
> 45 | __syslog_chk (__pri, __USE_FORTIFY_LEVEL - 1, __fmt, __va_arg_pack ());
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> Add a check that 'value' is not null before passing it to trace_xs_node_read().
>
> Fixes: e6cdeee95990 ("hw/xen: Add xs_node_read() helper function")
> Signed-off-by: Liam Merwick <liam.merwick@oracle.com>
Acked-by: Anthony PERARD <anthony.perard@vates.tech>
Thanks,
--
Anthony PERARD
next prev parent reply other threads:[~2025-05-26 16:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-23 16:01 [PATCH] hw/xen: Fix trace_xs_node_read() params Liam Merwick
2025-05-23 16:46 ` [EXTERNAL] " David Woodhouse
2025-05-26 16:19 ` Anthony PERARD [this message]
2025-05-26 18:10 ` Philippe Mathieu-Daudé
2025-05-27 7:22 ` Richard Henderson
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=aDSUesF-KUYnIoxM@l14 \
--to=anthony@xenproject.org \
--cc=dwmw@amazon.co.uk \
--cc=liam.merwick@oracle.com \
--cc=qemu-devel@nongnu.org \
--cc=roger.pau@citrix.com \
--cc=xen-devel@lists.xenproject.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).