From: Glenn Washburn <development@efficientek.com>
To: grub-devel@gnu.org, Daniel Kiper <dkiper@net-space.pl>,
"Vladimir 'phcoder' Serbinenko" <phcoder@gmail.com>
Cc: Glenn Washburn <development@efficientek.com>
Subject: [PATCH] misc: Make grub_vsnprintf C99/POSIX conformant
Date: Fri, 18 Aug 2023 12:15:27 -0500 [thread overview]
Message-ID: <20230818171527.2697491-1-development@efficientek.com> (raw)
To comply with C99 and POSIX standards, snprintf should return the
number of bytes that would be written to the string (excluding the
terminating NULL byte) if the buffer size was big enough. Before this
change, the return value was the minimum of the standard return and
the length of the buffer. Rarely is the return value of grub_snprintf
or grub_vsnprintf used with current code, and the few places where it is
used do not need to be changed.
Signed-off-by: Glenn Washburn <development@efficientek.com>
---
grub-core/kern/misc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/grub-core/kern/misc.c b/grub-core/kern/misc.c
index 95bf7860f3da..afb41bd63a6a 100644
--- a/grub-core/kern/misc.c
+++ b/grub-core/kern/misc.c
@@ -1201,7 +1201,7 @@ grub_vsnprintf (char *str, grub_size_t n, const char *fmt, va_list ap)
free_printf_args (&args);
- return ret < n ? ret : n;
+ return ret;
}
int
--
2.34.1
_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel
next reply other threads:[~2023-08-18 17:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-18 17:15 Glenn Washburn [this message]
2023-08-30 14:43 ` [PATCH] misc: Make grub_vsnprintf C99/POSIX conformant Daniel Kiper
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=20230818171527.2697491-1-development@efficientek.com \
--to=development@efficientek.com \
--cc=dkiper@net-space.pl \
--cc=grub-devel@gnu.org \
--cc=phcoder@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.