From: Manivannan Sadhasivam <mani@kernel.org>
To: "Krzysztof Wilczyński" <kwilczynski@kernel.org>,
"Kishon Vijay Abraham I" <kishon@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Niklas Cassel" <cassel@kernel.org>,
"Frank Li" <Frank.Li@nxp.com>,
"Damien Le Moal" <dlemoal@kernel.org>,
"Mohamed Khalfella" <khalfella@gmail.com>,
"Christian Bruel" <christian.bruel@foss.st.com>,
"Bhanu Seshu Kumar Valluri" <bhanuseshukumar@gmail.com>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
khalid@kernel.org,
linux-kernel-mentees@lists.linuxfoundation.org,
skhan@linuxfoundation.org, david.hunter.linux@gmail.com
Subject: Re: [PATCH v3] PCI: endpoint: pci-epf-test: Fix sleeping function being called from atomic context
Date: Sun, 26 Oct 2025 21:23:53 +0530 [thread overview]
Message-ID: <176149403315.9388.15839787422598934486.b4-ty@kernel.org> (raw)
In-Reply-To: <20251014024109.42287-1-bhanuseshukumar@gmail.com>
On Tue, 14 Oct 2025 08:11:09 +0530, Bhanu Seshu Kumar Valluri wrote:
> When Root Complex (RC) triggers a Doorbell MSI interrupt to Endpoint (EP)
> it triggers a warning in the EP. pci_endpoint kselftest target is
> compiled and used to run the Doorbell test in RC.
>
> BUG: sleeping function called from invalid context at kernel/locking/mutex.c:271
> Call trace:
> __might_resched+0x130/0x158
> __might_sleep+0x70/0x88
> mutex_lock+0x2c/0x80
> pci_epc_get_msi+0x78/0xd8
> pci_epf_test_raise_irq.isra.0+0x74/0x138
> pci_epf_test_doorbell_handler+0x34/0x50
>
> [...]
Applied, thanks!
[1/1] PCI: endpoint: pci-epf-test: Fix sleeping function being called from atomic context
commit: 25423cda145f9ed6ee4a72d9f2603ac2a4685e74
Best regards,
--
Manivannan Sadhasivam <mani@kernel.org>
prev parent reply other threads:[~2025-10-26 15:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-14 2:41 [PATCH v3] PCI: endpoint: pci-epf-test: Fix sleeping function being called from atomic context Bhanu Seshu Kumar Valluri
2025-10-16 16:50 ` Frank Li
2025-10-26 15:53 ` Manivannan Sadhasivam [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=176149403315.9388.15839787422598934486.b4-ty@kernel.org \
--to=mani@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=bhanuseshukumar@gmail.com \
--cc=bhelgaas@google.com \
--cc=cassel@kernel.org \
--cc=christian.bruel@foss.st.com \
--cc=david.hunter.linux@gmail.com \
--cc=dlemoal@kernel.org \
--cc=khalfella@gmail.com \
--cc=khalid@kernel.org \
--cc=kishon@kernel.org \
--cc=kwilczynski@kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=skhan@linuxfoundation.org \
/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