From: David Gibson <david@gibson.dropbear.id.au>
To: Yumei Huang <yuhuang@redhat.com>
Cc: passt-dev@passt.top, sbrivio@redhat.com
Subject: Re: [PATCH v3 2/4] util: Introduce read_file() and read_file_long() function
Date: Wed, 15 Oct 2025 10:27:45 +1100 [thread overview]
Message-ID: <aO7ccdjqy-ARM__s@zatzit> (raw)
In-Reply-To: <20251014073836.18150-3-yuhuang@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 5454 bytes --]
On Tue, Oct 14, 2025 at 03:38:34PM +0800, Yumei Huang wrote:
> Signed-off-by: Yumei Huang <yuhuang@redhat.com>
> ---
> util.c | 92 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> util.h | 2 ++
> 2 files changed, 94 insertions(+)
>
> diff --git a/util.c b/util.c
> index c492f90..d331f08 100644
> --- a/util.c
> +++ b/util.c
> @@ -579,6 +579,98 @@ int write_file(const char *path, const char *buf)
> return len == 0 ? 0 : -1;
> }
>
> +/**
> + * read_file() - Read contents of file into a buffer
> + * @path: File to read
> + * @buf: Buffer to store file contents
> + * @buf_size: Size of buffer
> + *
> + * Return: number of bytes read on success, -1 on any error, -2 on truncation
> +*/
Looks ok, but I think there's a simpler way.
> +int read_file(const char *path, char *buf, size_t buf_size)
> +{
> + int fd = open(path, O_RDONLY | O_CLOEXEC);
> + size_t total_read = 0;
> + ssize_t rc;
> + bool truncated = false;
> +
> + if (fd < 0) {
> + warn_perror("Could not open %s", path);
> + return -1;
> + }
> +
> + while (total_read < buf_size - 1) {
> + rc = read(fd, buf + total_read, buf_size - 1 - total_read);
The '- 1' is to leave space for the \0, but if you instead attempt to
read the entire buffer...
> +
> + if (rc < 0 ) {
(nit: extra space before ')')
> + warn_perror("Couldn't read from %s", path);
> + close(fd);
> + return -1;
> + }
> +
> + if (rc == 0) {
> + break;
> + }
> +
> + total_read += rc;
> +
> + if (total_read == buf_size - 1) {
> + char test_byte;
> + rc = read(fd, &test_byte, 1);
> + if (rc >0) {
> + truncated = true;
> + warn_perror("File %s truncated, buffer too small", path);
> + }
> + }
...then you can tell if you have to truncate by finishing the loop
then checking if (total_read < buf_size). If it is, there's space for
the \0, otherwise there isn't and you report truncation. No need for
test_byte.
> + }
> +
> + close(fd);
> +
> + if (total_read < buf_size){
> + buf[total_read] = '\0';
And if you test for truncation and exit early, you can make this
unconditional.
> + }
> +
> + return truncated ? -2 : (int)total_read;
> +}
> +
> +/**
> + * read_file_long() - Read a long integer value from a file
When I first read this name I thought it was for reading a long file,
rather than reading a long (int) from a file. Not immediately sure
how to clarify that. read_file_long_int() is clear, but awkward.
A better choice might be to change this to use strtoimax() and call it
read_file_integer().
> + * @path: Path to the sysctl file
> + * @fallback: Default value if file can't be read
> + *
> + * Return: Parameter value, fallback on failure
> +*/
> +long read_file_long(const char *path, long fallback)
> +{
> + char buf[32];
Rather than just using a semi-arbitrary 32 here, I'd suggest defining
a new constant similar to UINT16_STRLEN. Except that's trickier for a
type that doesn't have a known fixed width. Pity the C library
doesn't have constants for these AFAICT.
> + char *end;
> + long value;
> + int bytes_read;
> +
> + bytes_read = read_file(path, buf, sizeof(buf));
> + if (bytes_read < 0) {
> + debug("Unable to read %s", path);
If there's a an error on open() or read(), this will produce two very
similar error messages in a row, which isn't ideal.
> + return fallback;
> + }
> +
> + if (bytes_read == 0) {
> + debug("Empty file %s", path);
> + return fallback;
> + }
Might be worth checking strtol()'s behaviour on an empty string to see
if this special case would already be handled below.
> +
> + errno = 0;
> + value = strtol(buf, &end, 10);
> + if (*end && *end != '\n') {
> + debug("Invalid format in %s", path);
> + return fallback;
> + }
> + if (errno || value < 0 || value > LONG_MAX) {
No need to exclude negative values here. (value > LONG_MAX) can never
be true since value is a long.
> + debug("Invalid value in %s: %ld", path, value);
If errno != 0, value might be uninitialised here, and certainly won't
have something useful. Better to print the contents as a string.
> + return fallback;
> + }
> + return value;
> +}
> +
> #ifdef __ia64__
> /* Needed by do_clone() below: glibc doesn't export the prototype of __clone2(),
> * use the description from clone(2).
> diff --git a/util.h b/util.h
> index 22eaac5..e509bec 100644
> --- a/util.h
> +++ b/util.h
> @@ -222,6 +222,8 @@ void pidfile_write(int fd, pid_t pid);
> int __daemon(int pidfile_fd, int devnull_fd);
> int fls(unsigned long x);
> int write_file(const char *path, const char *buf);
> +int read_file(const char *path, char *buf, size_t buf_size);
> +long read_file_long(const char *path, long fallback);
> int write_all_buf(int fd, const void *buf, size_t len);
> int write_remainder(int fd, const struct iovec *iov, size_t iovcnt, size_t skip);
> int read_all_buf(int fd, void *buf, size_t len);
> --
> 2.47.0
>
--
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 --]
next prev parent reply other threads:[~2025-10-14 23:27 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-14 7:38 [PATCH v3 0/4] Retry SYNs for inbound connections Yumei Huang
2025-10-14 7:38 ` [PATCH v3 1/4] tcp: Rename "retrans" to "retries" Yumei Huang
2025-10-14 22:50 ` David Gibson
2025-10-15 2:17 ` Yumei Huang
2025-10-14 7:38 ` [PATCH v3 2/4] util: Introduce read_file() and read_file_long() function Yumei Huang
2025-10-14 23:27 ` David Gibson [this message]
2025-10-15 3:50 ` Yumei Huang
2025-10-15 4:46 ` David Gibson
2025-10-15 5:46 ` Yumei Huang
2025-10-28 23:12 ` Stefano Brivio
2025-10-29 0:43 ` David Gibson
2025-10-29 4:43 ` Stefano Brivio
2025-10-29 9:35 ` David Gibson
2025-10-29 16:23 ` Stefano Brivio
2025-10-14 7:38 ` [PATCH v3 3/4] tcp: Resend SYN for inbound connections Yumei Huang
2025-10-14 23:40 ` David Gibson
2025-10-14 7:38 ` [PATCH v3 4/4] tcp: Update data retransmission timeout Yumei Huang
2025-10-15 0:05 ` David Gibson
2025-10-15 6:31 ` Yumei Huang
2025-10-15 22:54 ` David Gibson
2025-10-17 18:28 ` Stefano Brivio
2025-10-20 0:20 ` David Gibson
2025-10-20 5:11 ` Stefano Brivio
2025-10-20 9:17 ` David Gibson
2025-10-28 23:13 ` Stefano Brivio
2025-10-29 0:35 ` David Gibson
2025-10-29 4:52 ` Stefano Brivio
2025-10-29 9:37 ` David Gibson
2025-10-20 10:57 ` Yumei Huang
2025-10-20 23:20 ` Stefano Brivio
2025-10-22 2:23 ` David Gibson
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=aO7ccdjqy-ARM__s@zatzit \
--to=david@gibson.dropbear.id.au \
--cc=passt-dev@passt.top \
--cc=sbrivio@redhat.com \
--cc=yuhuang@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).