From: Stefano Brivio <sbrivio@redhat.com>
To: Yumei Huang <yuhuang@redhat.com>
Cc: passt-dev@passt.top, david@gibson.dropbear.id.au
Subject: Re: [PATCH v8 2/6] util: Introduce read_file() and read_file_integer() function
Date: Tue, 18 Nov 2025 01:19:55 +0100 [thread overview]
Message-ID: <20251118011955.635ee70c@elisabeth> (raw)
In-Reply-To: <CANsz47mqy2G9sueYs6R1kBhF20hs4RV5G726q4iTHFGrpeQX0w@mail.gmail.com>
On Mon, 17 Nov 2025 09:10:01 +0800
Yumei Huang <yuhuang@redhat.com> wrote:
> On Fri, Nov 14, 2025 at 6:12 PM Stefano Brivio <sbrivio@redhat.com> wrote:
> >
> > On Fri, 14 Nov 2025 09:58:57 +0800
> > Yumei Huang <yuhuang@redhat.com> wrote:
> >
> > > On Fri, Nov 14, 2025 at 8:01 AM Stefano Brivio <sbrivio@redhat.com> wrote:
> > > >
> > > > On Mon, 10 Nov 2025 17:31:33 +0800
> > > > Yumei Huang <yuhuang@redhat.com> wrote:
> > > >
> > > > > Signed-off-by: Yumei Huang <yuhuang@redhat.com>
> > > > > Reviewed-by: David Gibson <david@gibson.dropbear.id.au>
> > > > > ---
> > > > > util.c | 86 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > > > > util.h | 2 ++
> > > > > 2 files changed, 88 insertions(+)
> > > > >
> > > > > diff --git a/util.c b/util.c
> > > > > index 44c21a3..c4c849c 100644
> > > > > --- a/util.c
> > > > > +++ b/util.c
> > > > > @@ -590,6 +590,92 @@ int write_file(const char *path, const char *buf)
> > > > > return len == 0 ? 0 : -1;
> > > > > }
> > > > >
> > > > > +/**
> > > > > + * read_file() - Read contents of file into a NULL-terminated buffer
> > > > > + * @path: Path to file to read
> > > > > + * @buf: Buffer to store file contents
> > > > > + * @buf_size: Size of buffer
> > > > > + *
> > > > > + * Return: number of bytes read on success, -1 on error, -ENOBUFS on truncation
> > > > > + */
> > > > > +ssize_t 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;
> > > > > +
> > > > > + if (fd < 0) {
> > > > > + warn_perror("Could not open %s", path);
> > > > > + return -1;
> > > > > + }
> > > > > +
> > > > > + while (total_read < buf_size) {
> > > > > + rc = read(fd, buf + total_read, buf_size - total_read);
> > > >
> > > > cppcheck rightfully says that:
> > > >
> > > > util.c:604:10: style: The scope of the variable 'rc' can be reduced. [variableScope]
> > > > ssize_t rc;
> > > > ^
> > >
> > > Right.
> > > Seems it also says:
> > >
> > > tcp.c:2814:0: style: The function 'tcp_get_rto_params' should have
> > > static linkage since it is not used outside of its translation unit.
> > > [staticFunction]
> > > void tcp_get_rto_params(struct ctx *c)
> > > ^
> > > util.c:601:0: style: The function 'read_file' should have static
> > > linkage since it is not used outside of its translation unit.
> > > [staticFunction]
> > > ssize_t read_file(const char *path, char *buf, size_t buf_size)
> >
> > Oops, my current version (2.16.0) doesn't say that, I should upgrade it
> > (but I typically try to remain a few versions behind as David usually
> > upgrades right away, so that we catch also differences).
> >
> > > I understand read_file() may be called from other places in the
> > > future. But do we need to add static now? I guess we need it for
> > > tcp_get_rto_params().
> >
> > On top of what David said, I'm not sure if we'll ever need it in
> > tcp_get_rto_params(): I guess we'll always want to read integers there.
>
> I meant we need to add static for tcp_get_rto_params().
Ah, yes, right, that one too, it's not used outside of tcp.c (its
compilation unit).
--
Stefano
next prev parent reply other threads:[~2025-11-18 0:20 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-10 9:31 [PATCH v8 0/6] Retry SYNs for inbound connections Yumei Huang
2025-11-10 9:31 ` [PATCH v8 1/6] tcp: Rename "retrans" to "retries" Yumei Huang
2025-11-10 9:31 ` [PATCH v8 2/6] util: Introduce read_file() and read_file_integer() function Yumei Huang
2025-11-14 0:01 ` Stefano Brivio
2025-11-14 1:58 ` Yumei Huang
2025-11-14 4:32 ` David Gibson
2025-11-14 10:12 ` Stefano Brivio
2025-11-17 1:10 ` Yumei Huang
2025-11-18 0:19 ` Stefano Brivio [this message]
2025-11-18 0:19 ` Stefano Brivio
2025-11-18 3:22 ` David Gibson
2025-11-19 9:04 ` Yumei Huang
2025-11-19 9:38 ` David Gibson
2025-11-10 9:31 ` [PATCH v8 3/6] tcp: Add parameter struct ctx *c to tcp_timer_ctl() Yumei Huang
2025-11-10 10:35 ` David Gibson
2025-11-14 0:01 ` Stefano Brivio
2025-11-14 0:36 ` David Gibson
2025-11-10 9:31 ` [PATCH v8 4/6] tcp: Resend SYN for inbound connections Yumei Huang
2025-11-10 10:46 ` David Gibson
2025-11-14 0:00 ` Stefano Brivio
2025-11-14 0:31 ` David Gibson
2025-11-18 0:19 ` Stefano Brivio
2025-11-10 9:31 ` [PATCH v8 5/6] tcp: Update data retransmission timeout Yumei Huang
2025-11-10 9:31 ` [PATCH v8 6/6] tcp: Clamp the retry timeout Yumei Huang
2025-11-10 10:56 ` David Gibson
2025-11-14 0:01 ` Stefano Brivio
2025-11-14 0:35 ` David Gibson
2025-11-14 3:05 ` Yumei Huang
2025-11-14 3:35 ` David Gibson
2025-11-17 2:38 ` Yumei Huang
2025-11-17 4:50 ` David Gibson
2025-11-18 0:19 ` Stefano Brivio
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=20251118011955.635ee70c@elisabeth \
--to=sbrivio@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=passt-dev@passt.top \
--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).