From: Madhavan Srinivasan <maddy@linux.ibm.com>
To: mpe@ellerman.id.au, npiggin@gmail.com, chleroy@kernel.org,
namcao@linutronix.de, peterz@infradead.org,
sshegde@linux.ibm.com, kees@kernel.org,
lgs201920130244@gmail.com, srikar@linux.ibm.com,
ynorov@nvidia.com, nilay@linux.ibm.com, clg@kaod.org,
benh@kernel.crashing.org, miltonm@bga.com, mkchauras@gmail.com,
akpm@linux-foundation.org, Gou Hao <gouhao@uniontech.com>
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
gouhaojake@163.com, kernel@uniontech.com
Subject: Re: [PATCH v3 0/5] powerpc/xive: remove __GFP_NOFAIL and fix IPI error handling
Date: Thu, 6 Aug 2026 09:46:16 +0530 [thread overview]
Message-ID: <178598971864.942627.7914448330996687839.b4-ty@linux.ibm.com> (raw)
In-Reply-To: <20260727104215.184786-1-gouhao@uniontech.com>
On Mon, 27 Jul 2026 18:42:10 +0800, Gou Hao wrote:
> Changes in v3:
> - Split into a separate xive-only series; the drm, test_hmm
> and cxgb4 patches are unchanged since v1 and will no longer be updated here.
> - Rework the first patch: instead of simply removing the unreachable
> NULL check, remove __GFP_NOFAIL from the IPI allocation and make
> all xive_ipis access paths NULL-safe (suggested by Andrew Morton [1]
> and Cédric Le Goater).
> - Add a patch to defer setting cause_ipi until IPI init succeeds,
> so that smp_muxed_ipi_message_pass() does not call into a
> half-initialized IPI path.
> - Add a defensive NULL guard for cause_ipi in
> smp_muxed_ipi_message_pass() as a safety net.
>
> [...]
Applied to powerpc/next.
[1/5] powerpc/xive: make xive IPI allocation NULL-safe
https://git.kernel.org/powerpc/c/f068fca7e8b7014014296b0e458ba9c5aa77f954
[2/5] powerpc/xive: add error return value to xive_smp_probe()
https://git.kernel.org/powerpc/c/ab5ae5dceb86614f6c9e7488f91b652000edfdc5
[3/5] powerpc/xive: propagate IPI init errors to prevent use-after-free
https://git.kernel.org/powerpc/c/411a3c016e7a95f5fa105a0587e07d0647a77727
[4/5] powerpc/xive: defer setting cause_ipi until IPI init succeeds
https://git.kernel.org/powerpc/c/37d401c9c4b89c3c193726e177493ef06c657f40
[5/5] powerpc/smp: add NULL guard for cause_ipi in smp_muxed_ipi_message_pass
https://git.kernel.org/powerpc/c/5aabc192702defb8950e7c81b05c3f4ca8ee43ec
cheers
prev parent reply other threads:[~2026-08-06 4:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-27 10:42 [PATCH v3 0/5] powerpc/xive: remove __GFP_NOFAIL and fix IPI error handling Gou Hao
2026-07-27 10:42 ` [PATCH v3 1/5] powerpc/xive: make xive IPI allocation NULL-safe Gou Hao
2026-07-30 13:53 ` Shrikanth Hegde
2026-07-30 14:06 ` Cédric Le Goater
2026-07-30 17:50 ` Shrikanth Hegde
2026-07-27 10:42 ` [PATCH v3 2/5] powerpc/xive: add error return value to xive_smp_probe() Gou Hao
2026-07-29 17:33 ` Cédric Le Goater
2026-07-27 10:42 ` [PATCH v3 3/5] powerpc/xive: propagate IPI init errors to prevent use-after-free Gou Hao
2026-07-28 2:47 ` Srikar Dronamraju
2026-07-28 10:26 ` Gou Hao
2026-07-29 17:37 ` Cédric Le Goater
2026-07-29 17:34 ` Cédric Le Goater
2026-07-27 10:42 ` [PATCH v3 4/5] powerpc/xive: defer setting cause_ipi until IPI init succeeds Gou Hao
2026-07-29 17:34 ` Cédric Le Goater
2026-07-27 10:42 ` [PATCH v3 5/5] powerpc/smp: add NULL guard for cause_ipi in smp_muxed_ipi_message_pass Gou Hao
2026-08-06 4:16 ` Madhavan Srinivasan [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=178598971864.942627.7914448330996687839.b4-ty@linux.ibm.com \
--to=maddy@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=chleroy@kernel.org \
--cc=clg@kaod.org \
--cc=gouhao@uniontech.com \
--cc=gouhaojake@163.com \
--cc=kees@kernel.org \
--cc=kernel@uniontech.com \
--cc=lgs201920130244@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=miltonm@bga.com \
--cc=mkchauras@gmail.com \
--cc=mpe@ellerman.id.au \
--cc=namcao@linutronix.de \
--cc=nilay@linux.ibm.com \
--cc=npiggin@gmail.com \
--cc=peterz@infradead.org \
--cc=srikar@linux.ibm.com \
--cc=sshegde@linux.ibm.com \
--cc=ynorov@nvidia.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