From: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
To: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
Cc: kishon@ti.com, lpieralisi@kernel.org, kw@linux.com,
bhelgaas@google.com, linux-pci@vger.kernel.org,
linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH] PCI: endpoint: Fix WARN() when an endpoint driver is removed
Date: Tue, 21 Jun 2022 19:50:58 +0530 [thread overview]
Message-ID: <20220621142058.GE17181@thinkpad> (raw)
In-Reply-To: <20220621121147.3971001-1-yoshihiro.shimoda.uh@renesas.com>
On Tue, Jun 21, 2022 at 09:11:47PM +0900, Yoshihiro Shimoda wrote:
> Add pci_epc_nop_release() for epc->dev.release. Otherwise,
> WARN() happened when a PCIe endpoint driver is removed.
>
> Device 'e65d0000.pcie-ep' does not have a release() function, it is broken and must be fixed. See Documentation/core-api/kobject.rst.
> WARNING: CPU: 0 PID: 139 at drivers/base/core.c:2232 device_release+0x78/0x8c
>
Hmm... So the core is correctly throwing the warning here but just using a NOP
release function is not the right solution IMO.
Currently, pci_epc_destroy() is handling all resource release including freeing
the memory for epc. But I think the "kfree(epc)" should be moved to this
release callback. Reason is quite obvious. Until the release() callback gets
called, there would be a "epc" device instance floating around and we should not
free it until then.
Thanks,
Mani
> Signed-off-by: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
> ---
> drivers/pci/endpoint/pci-epc-core.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/drivers/pci/endpoint/pci-epc-core.c b/drivers/pci/endpoint/pci-epc-core.c
> index 3bc9273d0a08..cb533821b072 100644
> --- a/drivers/pci/endpoint/pci-epc-core.c
> +++ b/drivers/pci/endpoint/pci-epc-core.c
> @@ -746,6 +746,10 @@ void devm_pci_epc_destroy(struct device *dev, struct pci_epc *epc)
> }
> EXPORT_SYMBOL_GPL(devm_pci_epc_destroy);
>
> +static void pci_epc_nop_release(struct device *dev)
> +{
> +}
> +
> /**
> * __pci_epc_create() - create a new endpoint controller (EPC) device
> * @dev: device that is creating the new EPC
> @@ -779,6 +783,7 @@ __pci_epc_create(struct device *dev, const struct pci_epc_ops *ops,
> device_initialize(&epc->dev);
> epc->dev.class = pci_epc_class;
> epc->dev.parent = dev;
> + epc->dev.release = pci_epc_nop_release;
> epc->ops = ops;
>
> ret = dev_set_name(&epc->dev, "%s", dev_name(dev));
> --
> 2.25.1
>
--
மணிவண்ணன் சதாசிவம்
next prev parent reply other threads:[~2022-06-21 14:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-21 12:11 [PATCH] PCI: endpoint: Fix WARN() when an endpoint driver is removed Yoshihiro Shimoda
2022-06-21 14:20 ` Manivannan Sadhasivam [this message]
2022-06-22 2:25 ` Yoshihiro Shimoda
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=20220621142058.GE17181@thinkpad \
--to=manivannan.sadhasivam@linaro.org \
--cc=bhelgaas@google.com \
--cc=kishon@ti.com \
--cc=kw@linux.com \
--cc=linux-pci@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=yoshihiro.shimoda.uh@renesas.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