From: John Kacur <jkacur@redhat.com>
To: Cheng-Yang Chou <yphbchou0911@gmail.com>
Cc: williams@redhat.com, linux-rt-users@vger.kernel.org,
jserv@ccns.ncku.edu.tw
Subject: Re: [PATCH v2 1/8] rt-utils.c: Check return values of write()
Date: Fri, 26 Sep 2025 13:38:06 -0400 (EDT) [thread overview]
Message-ID: <c09b8057-a037-20df-9b1d-2f7a65542231@redhat.com> (raw)
In-Reply-To: <20250726091837.493915-2-yphbchou0911@gmail.com>
On Sat, 26 Jul 2025, Cheng-Yang Chou wrote:
> Add error handling for write() to tracefs in tracemark() to avoid ignoring
> partial or failed writes.
>
> Signed-off-by: Cheng-Yang Chou <yphbchou0911@gmail.com>
> ---
> src/lib/rt-utils.c | 9 +++++++--
> 1 file changed, 7 insertions(+), 2 deletions(-)
>
> diff --git a/src/lib/rt-utils.c b/src/lib/rt-utils.c
> index 6bbd25a..447e158 100644
> --- a/src/lib/rt-utils.c
> +++ b/src/lib/rt-utils.c
> @@ -465,6 +465,7 @@ void tracemark(char *fmt, ...)
> {
> va_list ap;
> int len;
> + int ret;
>
> /* bail out if we're not tracing */
> /* or if the kernel doesn't support trace_mark */
> @@ -476,10 +477,14 @@ void tracemark(char *fmt, ...)
> va_end(ap);
>
> /* write the tracemark message */
> - write(tracemark_fd, tracebuf, len);
> + ret = write(tracemark_fd, tracebuf, len);
> + if (ret != len)
> + warn("%s: write failed", __func__);
>
> /* now stop any trace */
> - write(trace_fd, "0\n", 2);
> + ret = write(trace_fd, "0\n", 2);
> + if (ret != 2)
> + warn("trace stop write failed");
> }
>
> void enable_trace_mark(void)
> --
- resolved merge conflict because an earlier patch changed tracemark()
and tracing_stop() since this was submitted
Signed-off-by: John Kacur <jkacur@redhat.com>
next prev parent reply other threads:[~2025-09-26 17:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-26 9:18 [PATCH v2 0/8] Fix -Wunused-result warnings by checking return values Cheng-Yang Chou
2025-07-26 9:18 ` [PATCH v2 1/8] rt-utils.c: Check return values of write() Cheng-Yang Chou
2025-09-26 17:38 ` John Kacur [this message]
2025-07-26 9:18 ` [PATCH v2 2/8] pmqtest.c: Check return values of write() and ftruncate() Cheng-Yang Chou
2025-09-26 17:40 ` John Kacur
2025-07-26 9:18 ` [PATCH v2 3/8] ptsematest.c: " Cheng-Yang Chou
2025-09-26 17:57 ` John Kacur
2025-07-26 9:18 ` [PATCH v2 4/8] rt-migrate-test.c: " Cheng-Yang Chou
2025-09-26 19:49 ` John Kacur
2025-07-26 9:18 ` [PATCH v2 5/8] cyclicdeadline.c: " Cheng-Yang Chou
2025-09-26 19:58 ` John Kacur
2025-07-26 9:18 ` [PATCH v2 6/8] deadline_test.c: " Cheng-Yang Chou
2025-09-26 20:00 ` John Kacur
2025-07-26 9:18 ` [PATCH v2 7/8] sigwaittest.c: " Cheng-Yang Chou
2025-09-26 20:01 ` John Kacur
2025-07-26 9:18 ` [PATCH v2 8/8] svsematest.c: " Cheng-Yang Chou
2025-09-26 20:03 ` John Kacur
2025-08-07 16:26 ` [PATCH v2 0/8] Fix -Wunused-result warnings by checking return values Cheng-Yang Chou
2025-08-23 12:40 ` Cheng-Yang Chou
2025-09-05 18:27 ` Cheng-Yang Chou
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=c09b8057-a037-20df-9b1d-2f7a65542231@redhat.com \
--to=jkacur@redhat.com \
--cc=jserv@ccns.ncku.edu.tw \
--cc=linux-rt-users@vger.kernel.org \
--cc=williams@redhat.com \
--cc=yphbchou0911@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 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).