LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Nam Cao <namcao@linutronix.de>
To: Nilay Shroff <nilay@linux.ibm.com>
Cc: maddy@linux.ibm.com, mpe@ellerman.id.au, npiggin@gmail.com,
	christophe.leroy@csgroup.eu, tglx@linutronix.de, maz@kernel.org,
	gautam@linux.ibm.com, linuxppc-dev@lists.ozlabs.org,
	Linux List Kernel Mailing <linux-kernel@vger.kernel.org>,
	"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Subject: Re: [bug report][PPC]: rmod nvme driver causes the kernel panic
Date: Mon, 13 Oct 2025 12:00:42 +0200	[thread overview]
Message-ID: <87h5w3f7ed.fsf@yellow.woof> (raw)
In-Reply-To: <31838b50-e420-405a-af23-6c6ede281386@linux.ibm.com>

Nilay Shroff <nilay@linux.ibm.com> writes:
> Hi Nam,
Hi Nilay,

> On the latest upstream mainline kernel, I am encountering a kernel
> crash when attempting to unload the NVMe driver module (rmmod nvme)
> on a POWER9 system. The crash appears to be triggered by the recent
> work on using MSI parent domains, discussed here: 
> https://lore.kernel.org/all/cover.1754903590.git.namcao@linutronix.de/

Thanks for the detailed analysis. This should be fixed by:
https://lore.kernel.org/linuxppc-dev/20251010120307.3281720-1-namcao@linutronix.de/T/#u

which currently is in powerpc/fixes-test

> Possible Cause:
> ===============
> This looks like a cleanup ordering issue introduced by the recent MSI parent
> domain rework. The PCI/MSI teardown seems to assume that the MSI descriptor
> remains valid until after the domain teardown path executes — which no longer
> appears to hold true in this sequence.

I think the reason is more idiotic than that, the msi_alloc_info_t
passed to pseries_msi_ops_teardown() is always all zeroes, thus we have
the NULL pointer deref regardless of the sequence. See the patch I
mentioned.

Nam


  reply	other threads:[~2025-10-13 10:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-13  9:23 [bug report][PPC]: rmod nvme driver causes the kernel panic Nilay Shroff
2025-10-13 10:00 ` Nam Cao [this message]
2025-10-13 10:28   ` Nilay Shroff

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=87h5w3f7ed.fsf@yellow.woof \
    --to=namcao@linutronix.de \
    --cc=christophe.leroy@csgroup.eu \
    --cc=gautam@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=maddy@linux.ibm.com \
    --cc=maz@kernel.org \
    --cc=mpe@ellerman.id.au \
    --cc=nilay@linux.ibm.com \
    --cc=npiggin@gmail.com \
    --cc=tglx@linutronix.de \
    /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