From: Segher Boessenkool <segher@kernel.crashing.org>
To: Paulo Miguel Almeida <paulo.miguel.almeida.rodenas@gmail.com>
Cc: mpe@ellerman.id.au, npiggin@gmail.com,
christophe.leroy@csgroup.eu, naveen@kernel.org,
maddy@linux.ibm.com, arnd@arndb.de, chentao@kylinos.cn,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
linux-hardening@vger.kernel.org
Subject: Re: [PATCH][next] powerpc/spufs: Replace snprintf() with the safer scnprintf() variant
Date: Fri, 18 Oct 2024 23:13:29 -0500 [thread overview]
Message-ID: <20241019041329.GL29862@gate.crashing.org> (raw)
In-Reply-To: <ZxL0U6bziCxhySUO@mail.google.com>
Hi!
On Sat, Oct 19, 2024 at 12:50:43PM +1300, Paulo Miguel Almeida wrote:
> On Fri, Oct 18, 2024 at 10:38:43AM -0500, Segher Boessenkool wrote:
> > On Fri, Oct 18, 2024 at 09:28:19PM +1300, Paulo Miguel Almeida wrote:
> > > The C99 standard specifies that {v}snprintf() returns the length of the
> > > data that *would have been* written if there were enough space.
> >
> > Not including the trailing zero byte, and it can also return negative if
> > there was an encoding error. Yes.
> >
> > Not that this matters at all for your patch, so why mention it?
> >
> >
> > Segher
>
> Thanks for taking the time to review this patch.
>
> Is the objection with the change in itself or just the commit message?
Mostly the commit message. But because it is confusing, it makes the
patch itself uncertain as well.
The patch is probably fine fwiw, as far as I can see. But the commit
message is not. And the commit message is by far the most important
part of any patch!
> If it's the later, I'm happy to tweak it to what you would like see.
It is not about what I want to see. It is about what you want to say
to justify the patch!
In this case, just leave out all the irrelevant stuff, just say why you
think scnprintf is better than what you replace?
Everythihng you did say is about why what you are removing was good.
Not a great patch justification :-)
Segher
prev parent reply other threads:[~2024-10-19 4:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-18 8:28 [PATCH][next] powerpc/spufs: Replace snprintf() with the safer scnprintf() variant Paulo Miguel Almeida
2024-10-18 15:38 ` Segher Boessenkool
2024-10-18 23:50 ` Paulo Miguel Almeida
2024-10-19 4:13 ` Segher Boessenkool [this message]
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=20241019041329.GL29862@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=arnd@arndb.de \
--cc=chentao@kylinos.cn \
--cc=christophe.leroy@csgroup.eu \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=naveen@kernel.org \
--cc=npiggin@gmail.com \
--cc=paulo.miguel.almeida.rodenas@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).