From: Bjorn Helgaas <helgaas@kernel.org>
To: Daniel Stodden <dns@arista.com>
Cc: Dmitry Safonov <dima@arista.com>,
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 18:19:22 -0600 [thread overview]
Message-ID: <20231122001922.GA264028@bhelgaas> (raw)
In-Reply-To: <D34BC819-ACC4-4709-8464-73EEDDC64328@arista.com>
On Tue, Nov 21, 2023 at 03:58:22PM -0800, Daniel Stodden wrote:
> > 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
Happy to add that, no problem, but:
- "Signed-off-by" has a specific meaning about either being involved
in the creation of the patch or being part of the chain of
transmitting the patch, see
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?id=v6.6#n396
Since I got the patch directly from you, adding a signed-off-by
from dima@ would mean he created part of the patch.
- I don't think it makes sense to include both Signed-off-by and
Reviewed-by from the same person, since the point of Reviewed-by
is to get review by somebody other than the author.
- dima@ should include a name as well as the email address (I assume
"Dmitry Safonov <dima@arista.com>")
So if you want to use a Signed-off-by from Dmitry, please post a v4
including that (ideally starting from the commit above because I
silently fixed a couple other typos (although I missed the
put_device() thing)).
If you prefer a Dmitry's Reviewed-by, no need to post a v4. The best
thing would be for Dmitry to respond with the Reviewed-by on the
mailing list. Some people do collect reviews internally, but I prefer
to get them directly from the reviewer.
Bjorn
next prev parent reply other threads:[~2023-11-22 0:19 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
2023-11-22 0:02 ` Daniel Stodden
2023-11-22 0:39 ` Bjorn Helgaas
2023-11-22 0:19 ` Bjorn Helgaas [this message]
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=20231122001922.GA264028@bhelgaas \
--to=helgaas@kernel.org \
--cc=dima@arista.com \
--cc=dns@arista.com \
--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