From: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
To: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
Cc: Krzysztof Wilczynski <kw@linux.com>,
Kishon Vijay Abraham I <kishon@kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
Gustavo Pimentel <gustavo.pimentel@synopsys.com>,
Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH v3 1/5] misc: pci_endpoint_test: Avoid issue of interrupts remaining after request_irq error
Date: Fri, 14 Feb 2025 22:51:38 +0530 [thread overview]
Message-ID: <20250214172138.setswcgqz3dbf65t@thinkpad> (raw)
In-Reply-To: <20250210075812.3900646-2-hayashi.kunihiko@socionext.com>
On Mon, Feb 10, 2025 at 04:58:08PM +0900, Kunihiko Hayashi wrote:
> After devm_request_irq() fails with error in
> pci_endpoint_test_request_irq(), pci_endpoint_test_free_irq_vectors() is
> called assuming that all IRQs have been released.
>
> However some requested IRQs remain unreleased, so there are still
> /proc/irq/* entries remaining and we encounters WARN() with the following
s/we encounters/this results in WARN()
> message:
>
> remove_proc_entry: removing non-empty directory 'irq/30', leaking at
> least 'pci-endpoint-test.0'
> WARNING: CPU: 0 PID: 202 at fs/proc/generic.c:719 remove_proc_entry
> +0x190/0x19c
>
> And show the call trace that led to this issue:
You can remove this backtrace.
>
> [ 12.050005] Call trace:
> [ 12.051226] remove_proc_entry+0x190/0x19c (P)
> [ 12.053448] unregister_irq_proc+0xd0/0x104
> [ 12.055541] free_desc+0x4c/0xd0
> [ 12.057155] irq_free_descs+0x68/0x90
> [ 12.058984] irq_domain_free_irqs+0x15c/0x1bc
> [ 12.061161] msi_domain_free_locked.part.0+0x184/0x1d4
> [ 12.063728] msi_domain_free_irqs_all_locked+0x64/0x8c
> [ 12.066296] pci_msi_teardown_msi_irqs+0x48/0x54
> [ 12.068604] pci_free_msi_irqs+0x18/0x38
> [ 12.070564] pci_free_irq_vectors+0x64/0x8c
> [ 12.072654] pci_endpoint_test_ioctl+0x870/0x1068
> [ 12.075006] __arm64_sys_ioctl+0xb0/0xe8
> [ 12.076967] invoke_syscall+0x48/0x110
> [ 12.078841] el0_svc_common.constprop.0+0x40/0xe8
> [ 12.081192] do_el0_svc+0x20/0x2c
> [ 12.082848] el0_svc+0x30/0xd0
> [ 12.084376] el0t_64_sync_handler+0x144/0x168
> [ 12.086553] el0t_64_sync+0x198/0x19c
> [ 12.088383] ---[ end trace 0000000000000000 ]---
>
> To solve this issue, set the number of remaining IRQs to test->num_irqs
> and release IRQs in advance by calling pci_endpoint_test_release_irq().
>
> Cc: stable@vger.kernel.org
> Fixes: e03327122e2c ("pci_endpoint_test: Add 2 ioctl commands")
> Signed-off-by: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
Reviewed-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
- Mani
> ---
> drivers/misc/pci_endpoint_test.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/misc/pci_endpoint_test.c b/drivers/misc/pci_endpoint_test.c
> index d5ac71a49386..bbcccd425700 100644
> --- a/drivers/misc/pci_endpoint_test.c
> +++ b/drivers/misc/pci_endpoint_test.c
> @@ -259,6 +259,9 @@ static int pci_endpoint_test_request_irq(struct pci_endpoint_test *test)
> break;
> }
>
> + test->num_irqs = i;
> + pci_endpoint_test_release_irq(test);
> +
> return ret;
> }
>
> --
> 2.25.1
>
--
மணிவண்ணன் சதாசிவம்
next prev parent reply other threads:[~2025-02-14 17:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-10 7:58 [PATCH v3 0/5] Fix some issues related to an interrupt type in pci_endpoint_test Kunihiko Hayashi
2025-02-10 7:58 ` [PATCH v3 1/5] misc: pci_endpoint_test: Avoid issue of interrupts remaining after request_irq error Kunihiko Hayashi
2025-02-14 17:21 ` Manivannan Sadhasivam [this message]
2025-02-17 11:24 ` Kunihiko Hayashi
2025-02-10 7:58 ` [PATCH v3 2/5] misc: pci_endpoint_test: Fix disyplaying irq_type " Kunihiko Hayashi
2025-02-10 7:58 ` [PATCH v3 3/5] misc: pci_endpoint_test: Fix irq_type to convey the correct type Kunihiko Hayashi
2025-02-10 16:01 ` Niklas Cassel
2025-02-13 10:21 ` Kunihiko Hayashi
2025-02-13 13:26 ` Niklas Cassel
2025-02-14 17:25 ` Manivannan Sadhasivam
2025-02-17 11:26 ` Kunihiko Hayashi
2025-02-20 7:41 ` Manivannan Sadhasivam
2025-02-10 7:58 ` [PATCH v3 4/5] misc: pci_endpoint_test: Remove global irq_type Kunihiko Hayashi
2025-02-10 16:30 ` Niklas Cassel
2025-02-13 10:21 ` Kunihiko Hayashi
2025-02-14 17:27 ` Manivannan Sadhasivam
2025-02-10 7:58 ` [PATCH v3 5/5] misc: pci_endpoint_test: Do not use managed irq functions Kunihiko Hayashi
2025-02-14 17:29 ` Manivannan Sadhasivam
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=20250214172138.setswcgqz3dbf65t@thinkpad \
--to=manivannan.sadhasivam@linaro.org \
--cc=arnd@arndb.de \
--cc=bhelgaas@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=gustavo.pimentel@synopsys.com \
--cc=hayashi.kunihiko@socionext.com \
--cc=kishon@kernel.org \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=stable@vger.kernel.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