LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Kees Cook <kees@kernel.org>
To: Madhavan Srinivasan <maddy@linux.ibm.com>
Cc: "Bill Wendling" <morbo@google.com>,
	"Christophe Leroy (CS GROUP)" <chleroy@kernel.org>,
	"Uwe Kleine-König" <u.kleine-koenig@baylibre.com>,
	linuxppc-dev@lists.ozlabs.org,
	"Michael Ellerman" <mpe@ellerman.id.au>,
	"Nicholas Piggin" <npiggin@gmail.com>,
	"Shivaprasad G Bhat" <sbhat@linux.ibm.com>,
	"Thorsten Blum" <blum@kernel.org>,
	"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
	"Steven Rostedt" <rostedt@goodmis.org>,
	nikitash.mariiaw@gmail.com,
	"Greg KH" <gregkh@linuxfoundation.org>,
	linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH v3 09/11] powerpc/papr_scm: Return the string length from the sysfs show functions
Date: Fri, 2 Oct 2026 00:54:09 -0700	[thread overview]
Message-ID: <202610020052.9EAB79E@keescook> (raw)
In-Reply-To: <9af9f47d-b99e-46d4-bb6c-06d28b037a34@linux.ibm.com>

On Thu, Oct 01, 2026 at 09:47:56AM +0530, Madhavan Srinivasan wrote:
> 
> On 10/1/26 5:22 AM, Kees Cook wrote:
> > perf_stats_show() and flags_show() build their output with a seq_buf
> > and return seq_buf_used(), which may include the trailing NUL byte
> > when the seq_buf has overflowed. Use seq_buf_strlen() instead.
> > 
> > Build tested ARCH=powerpc ppc64_defconfig with GCC powerpc64-linux-gnu
> > 16.1.0:
> > arch/powerpc/platforms/pseries/papr_scm.o
> > 
> > Assisted-by: LLM
> > Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> > Signed-off-by: Kees Cook <kees@kernel.org>
> > ---
> >   arch/powerpc/platforms/pseries/papr_scm.c | 4 ++--
> >   1 file changed, 2 insertions(+), 2 deletions(-)
> > 
> > diff --git a/arch/powerpc/platforms/pseries/papr_scm.c b/arch/powerpc/platforms/pseries/papr_scm.c
> > index 75da96c08cdd..b03cfd8528f5 100644
> > --- a/arch/powerpc/platforms/pseries/papr_scm.c
> > +++ b/arch/powerpc/platforms/pseries/papr_scm.c
> > @@ -1108,7 +1108,7 @@ static ssize_t perf_stats_show(struct device *dev,
> >   free_stats:
> >   	kfree(stats);
> > -	return rc ? rc : (ssize_t)seq_buf_used(&s);
> > +	return rc ?: (ssize_t)seq_buf_strlen(&s);
> >   }
> >   static DEVICE_ATTR_ADMIN_RO(perf_stats);
> > @@ -1150,7 +1150,7 @@ static ssize_t flags_show(struct device *dev,
> >   	if (seq_buf_used(&s))
> 
> this can also be seq_buf_strlen instead

It could be, yeah. I left it because it seemed be more about "did we
touch this at all?" But it's honestly all the same. I will respin with
it changed too.

> 
> >   		seq_buf_printf(&s, "\n");
> > -	return seq_buf_used(&s);
> > +	return seq_buf_strlen(&s);
> >   }
> >   DEVICE_ATTR_RO(flags);

-- 
Kees Cook


      reply	other threads:[~2026-10-02  7:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20260930235231.out.387-kees@kernel.org>
2026-09-30 23:52 ` [PATCH v3 09/11] powerpc/papr_scm: Return the string length from the sysfs show functions Kees Cook
2026-10-01  4:17   ` Madhavan Srinivasan
2026-10-02  7:54     ` Kees Cook [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=202610020052.9EAB79E@keescook \
    --to=kees@kernel.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=blum@kernel.org \
    --cc=chleroy@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-hardening@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=maddy@linux.ibm.com \
    --cc=morbo@google.com \
    --cc=mpe@ellerman.id.au \
    --cc=nikitash.mariiaw@gmail.com \
    --cc=npiggin@gmail.com \
    --cc=rostedt@goodmis.org \
    --cc=sbhat@linux.ibm.com \
    --cc=u.kleine-koenig@baylibre.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