From: Daniel Stodden <dns@arista.com>
To: Bjorn Helgaas <helgaas@kernel.org>, Dmitry Safonov <dima@arista.com>
Cc: Kurt Schwemmer <kurt.schwemmer@microsemi.com>,
Logan Gunthorpe <logang@deltatee.com>,
linux-pci@vger.kernel.org
Subject: Re: [PATCH v3] switchtec: Fix stdev_release crash after suprise device loss.
Date: Tue, 21 Nov 2023 15:58:22 -0800 [thread overview]
Message-ID: <D34BC819-ACC4-4709-8464-73EEDDC64328@arista.com> (raw)
In-Reply-To: <20231121184008.GA249064@bhelgaas>
> On Nov 21, 2023, at 10:40 AM, Bjorn Helgaas <helgaas@kernel.org> wrote:
>
> On Tue, Nov 21, 2023 at 10:23:51AM -0800, Daniel Stodden wrote:
>>> On Nov 20, 2023, at 1:25 PM, Bjorn Helgaas <helgaas@kernel.org> wrote:
>>> On Mon, Nov 13, 2023 at 01:21:50PM -0800, Daniel Stodden wrote:
>>>> A pci device hot removal may occur while stdev->cdev is held open. The
>>>> call to stdev_release is then delivered during close or exit, at a
>>>> point way past switchtec_pci_remove. Otherwise the last ref would
>>>> vanish with the trailing put_device, just before return.
>>>>
>>>> At that later point in time, the device layer has alreay removed
>>>> stdev->mrpc_mmio map. Also, the stdev->pdev reference was not a
>>>
>>> I guess this should say the "stdev->mmio_mrpc" (not "mrpc_mmio")?
>>
>> Eww. My fault. Could you still correct that?
>
> Yep, I speculatively made that change already, so thanks for
> confirming it :)
>
> https://git.kernel.org/pub/scm/linux/kernel/git/pci/pci.git/commit/?h=switchtec&id=f9724598e29d
Thanks. And sorry for what’s next.
Look what I just found in my internal review inbox.
Signed-off/Reviewed-by: dima@arista.com
Want a v4, a follow-up, or can you re-edit that once more too, please?
Thanks + sorry,
Daniel
diff --git a/drivers/pci/switch/switchtec.c b/drivers/pci/switch/switchtec.c
index a82576205..ddaf87e10 100644
--- a/drivers/pci/switch/switchtec.c
+++ b/drivers/pci/switch/switchtec.c
@@ -1331,6 +1331,7 @@ static struct switchtec_dev *stdev_create(struct pci_dev *pdev)
err_put:
put_device(&stdev->dev);
+ put_device(&stdev->pdev);
return ERR_PTR(rc);
}
next prev parent reply other threads:[~2023-11-21 23:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-13 21:21 [PATCH v3 0/1] switchtec: Fix stdev_release crash after suprise device loss Daniel Stodden
2023-11-13 21:21 ` [PATCH v3] " Daniel Stodden
2023-11-20 21:25 ` Bjorn Helgaas
2023-11-21 18:23 ` Daniel Stodden
2023-11-21 18:40 ` Bjorn Helgaas
2023-11-21 23:58 ` Daniel Stodden [this message]
2023-11-22 0:02 ` Daniel Stodden
2023-11-22 0:39 ` Bjorn Helgaas
2023-11-22 0:19 ` Bjorn Helgaas
2023-11-22 0:25 ` Dmitry Safonov
2023-11-22 0:37 ` Bjorn Helgaas
2023-11-22 0:37 ` Dmitry Safonov
2023-11-22 0:41 ` Bjorn Helgaas
2023-11-22 1:02 ` Daniel Stodden
2023-11-22 3:16 ` Bjorn Helgaas
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=D34BC819-ACC4-4709-8464-73EEDDC64328@arista.com \
--to=dns@arista.com \
--cc=dima@arista.com \
--cc=helgaas@kernel.org \
--cc=kurt.schwemmer@microsemi.com \
--cc=linux-pci@vger.kernel.org \
--cc=logang@deltatee.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