From: Thomas Tai <thomas.tai@oracle.com>
To: thomas.tai@oracle.com, bhelgaas@google.com, keith.busch@intel.com
Cc: linux-pci@vger.kernel.org, poza@codeaurora.org
Subject: [PATCH V3, 0/1] PCI/AER: fix use-after-free in pcie_do_fatal_recovery
Date: Thu, 19 Jul 2018 14:02:34 -0600 [thread overview]
Message-ID: <1532030555-7177-1-git-send-email-thomas.tai@oracle.com> (raw)
Hi Bjorn,
I reworked the patch as suggested, would you please kindly
review the patch? By the way, the use-after-free issue would not
impact DPC, according to PCI Express Base Specification
Revision 4.0 Version 0.3 The DPC "capability may be
implemented by a Root Port or a Switch Downstream Port.
It is not applicable to any other Device/Port type."
The use-after-free only happens on a non-bridge device, so
it won't impact root/switch port.
Thank you very much.
Thomas
next reply other threads:[~2018-07-19 20:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-19 20:02 Thomas Tai [this message]
2018-07-19 20:02 ` [PATCH V3, 1/1] PCI/AER: fix use-after-free in pcie_do_fatal_recovery Thomas Tai
2018-07-25 20:24 ` Bjorn Helgaas
2018-07-26 14:29 ` Thomas Tai
2018-07-26 17:18 ` Bjorn Helgaas
2018-07-26 17:23 ` Thomas Tai
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=1532030555-7177-1-git-send-email-thomas.tai@oracle.com \
--to=thomas.tai@oracle.com \
--cc=bhelgaas@google.com \
--cc=keith.busch@intel.com \
--cc=linux-pci@vger.kernel.org \
--cc=poza@codeaurora.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;
as well as URLs for NNTP newsgroup(s).