From: Dan Carpenter <dan.carpenter@linaro.org>
To: Sun Jian <sun.jian.kdev@gmail.com>
Cc: Vaibhav Agarwal <vaibhav.sr@gmail.com>,
Johan Hovold <johan@kernel.org>,
Mark Greer <mgreer@animalcreek.com>,
Alex Elder <elder@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
David Laight <david.laight.linux@gmail.com>,
greybus-dev@lists.linaro.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] staging: greybus: audio: avoid snprintf truncation warnings
Date: Mon, 5 Jan 2026 14:55:37 +0300 [thread overview]
Message-ID: <aVumucN_RFQwfgj9@stanley.mountain> (raw)
In-Reply-To: <20251230012908.214959-1-sun.jian.kdev@gmail.com>
This W=1 string truncation warnings always seems like a pointless thing.
dmesg output is really only intended for developers. I don't even know
how to look at the dmesg on my phone or kindle. Who cares if the last
character in a really long device name is missing? I have looked at a
lot of stack traces and I have never once been stymied because one
character was missing in a really long device name.
And also these are 90% false positives. We just add bounds checking all
of our output to prevent memory corruption and not because we think that
we'll actually hit the boundaries. And the GCC is not able to analyze
these in a sensible way, it's just going based on the variable types.
This patch makes the code worse (more complicated).
To recap:
1: It's warning about a non-issue. No one cares about truncated output.
2: The warning is implemented poorly. High false positive ratio.
3: The fix makes the code worse
Just fix the tool instead of making the code worse for no reason.
regards,
dan carpenter
next prev parent reply other threads:[~2026-01-05 11:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-29 11:26 [PATCH] staging: greybus: audio: avoid snprintf truncation warnings Sun Jian
2025-12-29 14:17 ` David Laight
2025-12-29 16:13 ` [PATCH v2] " Sun Jian
2025-12-29 16:52 ` Greg Kroah-Hartman
2025-12-30 1:29 ` [PATCH v3] " Sun Jian
2025-12-30 7:40 ` Greg Kroah-Hartman
2025-12-30 22:20 ` David Laight
2026-01-05 11:55 ` Dan Carpenter [this message]
2026-01-05 15:37 ` sun jian
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=aVumucN_RFQwfgj9@stanley.mountain \
--to=dan.carpenter@linaro.org \
--cc=david.laight.linux@gmail.com \
--cc=elder@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=greybus-dev@lists.linaro.org \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=mgreer@animalcreek.com \
--cc=sun.jian.kdev@gmail.com \
--cc=vaibhav.sr@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