From: Xixin Liu <liuxixin@kylinos.cn>
To: linuxppc-dev@lists.ozlabs.org
Cc: maddy@linux.ibm.com, mpe@ellerman.id.au, npiggin@gmail.com,
chleroy@kernel.org, linux-kernel@vger.kernel.org,
liuxixin@kylinos.cn
Subject: [PATCH v1 0/4] powerpc: assorted fixes (gpci, imc, energy, iommu)
Date: Fri, 07 Aug 2026 11:11:14 +0800 [thread overview]
Message-ID: <cover.1786072274.git.liuxixin@kylinos.cn> (raw)
Hi,
This series fixes some bugs in powerpc paths found by static review
of linux-next:
1) hv-gpci sysfs hex formatting can overflow the PAGE_SIZE show
buffer; switch to sysfs_emit_at() and return -EFBIG
2) opal-imc debugfs names use char[16] with sprintf for a u32 id
3) pseries energy walks H_BEST_ENERGY cnt and sprintf()s without
page bounds
4) iommu debugfs uses char[10] with %08lx while it_index is
unsigned long
Patches are independent. Please review.
Thanks,
Xixin Liu
---
Xixin Liu (4):
powerpc/perf: hv-gpci: bound sysfs hex formatting to PAGE_SIZE
powerpc/powernv: opal-imc: fix debugfs name buffer size
powerpc/pseries: energy: bound H_BEST_ENERGY cnt and sysfs output
powerpc/iommu: fix debugfs name buffer for 64-bit it_index
arch/powerpc/kernel/iommu.c | 9 +++--
arch/powerpc/perf/hv-gpci.c | 77 +++++++++++++++---------
arch/powerpc/platforms/powernv/opal-imc.c | 7 +++--
arch/powerpc/platforms/pseries/pseries_energy.c | 16 ++++-
4 files changed, 75 insertions(+), 34 deletions(-)
--
2.43.0
next reply other threads:[~2026-08-07 3:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-07 3:11 Xixin Liu [this message]
2026-08-07 3:11 ` [PATCH v1 3/4] powerpc/pseries: energy: bound H_BEST_ENERGY cnt and sysfs output Xixin Liu
2026-08-07 3:11 ` [PATCH v1 2/4] powerpc/powernv: opal-imc: fix debugfs name buffer size Xixin Liu
2026-08-07 3:11 ` [PATCH v1 1/4] powerpc/perf: hv-gpci: bound sysfs hex formatting to PAGE_SIZE Xixin Liu
2026-08-07 3:11 ` [PATCH v1 4/4] powerpc/iommu: fix debugfs name buffer for 64-bit it_index Xixin Liu
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=cover.1786072274.git.liuxixin@kylinos.cn \
--to=liuxixin@kylinos.cn \
--cc=chleroy@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=npiggin@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