From: "Arnd Bergmann" <arnd@arndb.de>
To: "Junrui Luo" <moonafterrain@outlook.com>
Cc: "Madhavan Srinivasan" <maddy@linux.ibm.com>,
"Michael Ellerman" <mpe@ellerman.id.au>,
"Nicholas Piggin" <npiggin@gmail.com>,
"Christophe Leroy" <chleroy@kernel.org>,
"Paul Mackerras" <paulus@ozlabs.org>,
"Alexander Viro" <viro@zeniv.linux.org.uk>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Yuhao Jiang" <danisjiang@gmail.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH 0/6] powerpc/spufs: assorted fixes
Date: Mon, 03 Aug 2026 12:18:09 +0200 [thread overview]
Message-ID: <8391ed30-d739-49b2-ae8c-d31f01343841@app.fastmail.com> (raw)
In-Reply-To: <9E49BF8D-34E4-449A-A24A-AACCF6215DAF@outlook.com>
On Mon, Aug 3, 2026, at 11:59, Junrui Luo wrote:
> On Mon, Aug 03, 2026 at 11:28:46AM +0200, Arnd Bergmann wrote:
>> On Sun, Aug 2, 2026, at 17:51, Junrui Luo via B4 Relay wrote:
>> >
>> > Patches 1-5 are tagged for stable. 6/6 is deliberately not: it changes the
>> > atomicity of multi-element mailbox transfers rather than just adding a
>> > check, so it seems better to let it soak in mainline first.
>> >
>> > Build-tested only. I have no Cell or PS3 hardware, so none of this has
>> > been exercised at runtime.
>>
>> These are all reasonable fixes as far as I can tell, but I'm missing
>> information about why you care about spufs. If you used some atomated
>> tooling, please add some reference to what you used.
>
> We're working on a paper on LLM-assisted vulnerability research. spufs
> was just picked at random as one of the modules to look at. The tooling
> is an agent we developed ourselves. Should we add an Assisted-by tag in
> v2?
Yes, I think that would help.
Arnd
prev parent reply other threads:[~2026-08-03 10:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-02 15:51 [PATCH 0/6] powerpc/spufs: assorted fixes Junrui Luo via B4 Relay
2026-08-02 15:51 ` [PATCH 1/6] powerpc/spufs: fix spu_context leak in coredump Junrui Luo via B4 Relay
2026-08-03 9:05 ` Arnd Bergmann
2026-08-02 15:51 ` [PATCH 2/6] powerpc/spufs: don't leak kernel stack via spu_run Junrui Luo via B4 Relay
2026-08-03 9:09 ` Arnd Bergmann
2026-08-02 15:51 ` [PATCH 3/6] powerpc/spufs: bound NPC against local store size Junrui Luo via B4 Relay
2026-08-03 9:14 ` Arnd Bergmann
2026-08-04 6:30 ` Junrui Luo
2026-08-02 15:51 ` [PATCH 4/6] powerpc/spufs: check permissions in spufs_setattr() Junrui Luo via B4 Relay
2026-08-03 9:16 ` Arnd Bergmann
2026-08-02 15:51 ` [PATCH 5/6] powerpc/spufs: fix deadlock on gang creation failure Junrui Luo via B4 Relay
2026-08-02 15:51 ` [PATCH 6/6] powerpc/spufs: don't hold state_mutex during user access Junrui Luo via B4 Relay
2026-08-03 9:26 ` Arnd Bergmann
2026-08-03 9:28 ` [PATCH 0/6] powerpc/spufs: assorted fixes Arnd Bergmann
2026-08-03 9:59 ` Junrui Luo
2026-08-03 10:18 ` Arnd Bergmann [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=8391ed30-d739-49b2-ae8c-d31f01343841@app.fastmail.com \
--to=arnd@arndb.de \
--cc=chleroy@kernel.org \
--cc=danisjiang@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=moonafterrain@outlook.com \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=paulus@ozlabs.org \
--cc=stable@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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).