From: David Gibson <david@gibson.dropbear.id.au>
To: Stefano Brivio <sbrivio@redhat.com>
Cc: passt-dev@passt.top
Subject: Re: [PATCH] passt-repair: Fix build with -Werror=format-security
Date: Wed, 19 Mar 2025 11:36:56 +1100 [thread overview]
Message-ID: <Z9oRqB3f4gV4DiYA@zatzit> (raw)
In-Reply-To: <20250318195745.805417-1-sbrivio@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1303 bytes --]
On Tue, Mar 18, 2025 at 08:57:45PM +0100, Stefano Brivio wrote:
> Fixes: 04701702471e ("passt-repair: Add directory watch")
> Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
Reviewed-by: David Gibson <david@gibson.dropbear.id.au>
> ---
> Note: I just pushed this for my own sanity, as it's trivial and builds
> are otherwise broken on CentOS Stream / RHEL. I'm posting for review
> anyway in the unlikely case something can ever be wrong with this.
Looks like a good idea. Wonder if it's a good idea to turn on
-Wformat-security for upstream builds.
>
> passt-repair.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/passt-repair.c b/passt-repair.c
> index 8bb3f00..120f7aa 100644
> --- a/passt-repair.c
> +++ b/passt-repair.c
> @@ -150,7 +150,7 @@ int main(int argc, char **argv)
> _exit(1);
> }
>
> - ret = snprintf(a.sun_path, sizeof(a.sun_path), path);
> + ret = snprintf(a.sun_path, sizeof(a.sun_path), "%s", path);
> inotify_dir = true;
> } else {
> ret = snprintf(a.sun_path, sizeof(a.sun_path), "%s", argv[1]);
--
David Gibson (he or they) | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you, not the other way
| around.
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2025-03-19 0:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-18 19:57 [PATCH] passt-repair: Fix build with -Werror=format-security Stefano Brivio
2025-03-19 0:36 ` David Gibson [this message]
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=Z9oRqB3f4gV4DiYA@zatzit \
--to=david@gibson.dropbear.id.au \
--cc=passt-dev@passt.top \
--cc=sbrivio@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.
Code repositories for project(s) associated with this public inbox
https://passt.top/passt
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 IMAP folder(s).