public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: Will Deacon <will@kernel•org>
To: Catalin Marinas <catalin.marinas@arm•com>,
	shechenglong <shechenglong@xfusion•com>,
	Zenghui Yu <zenghui.yu@linux•dev>,
	Kuninori Morimoto <kuninori.morimoto.gx@renesas•com>,
	Jonathan Marek <jonathan@marek•ca>,
	Jinqian Yang <yangjinqian1@huawei•com>,
	Thorsten Blum <thorsten.blum@linux•dev>
Cc: kernel-team@android•com, Will Deacon <will@kernel•org>,
	linux-arm-kernel@lists•infradead.org,
	linux-kernel@vger•kernel.org
Subject: Re: [PATCH] arm64: proton-pack: use sysfs_emit in sysfs show functions
Date: Tue, 19 May 2026 16:23:10 +0100	[thread overview]
Message-ID: <177918937253.754805.7037838371679179364.b4-ty@kernel.org> (raw)
In-Reply-To: <20260513115756.447661-2-thorsten.blum@linux.dev>

On Wed, 13 May 2026 13:57:55 +0200, Thorsten Blum wrote:
> Replace sprintf() with sysfs_emit() in sysfs show functions, which is
> preferred for formatting sysfs output because it provides safer bounds
> checking.
> 
> While the current code only emits fixed strings that fit easily within
> PAGE_SIZE, use sysfs_emit() to follow secure coding best practices.
> 
> [...]

Applied to arm64 (for-next/errata), thanks!

[1/1] arm64: proton-pack: use sysfs_emit in sysfs show functions
      https://git.kernel.org/arm64/c/243c1d75a01e

Cheers,
-- 
Will

https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev


      reply	other threads:[~2026-05-19 15:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-13 11:57 [PATCH] arm64: proton-pack: use sysfs_emit in sysfs show functions Thorsten Blum
2026-05-19 15:23 ` Will Deacon [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=177918937253.754805.7037838371679179364.b4-ty@kernel.org \
    --to=will@kernel$(echo .)org \
    --cc=catalin.marinas@arm$(echo .)com \
    --cc=jonathan@marek$(echo .)ca \
    --cc=kernel-team@android$(echo .)com \
    --cc=kuninori.morimoto.gx@renesas$(echo .)com \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=shechenglong@xfusion$(echo .)com \
    --cc=thorsten.blum@linux$(echo .)dev \
    --cc=yangjinqian1@huawei$(echo .)com \
    --cc=zenghui.yu@linux$(echo .)dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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