From: Keith Busch <keith.busch@intel.com>
To: Alex_Gagniuc@Dellteam.com
Cc: linux-pci@vger.kernel.org, bhelgaas@google.com, scott.bauer@intel.com
Subject: Re: [PATCH 0/4] PCI/AER: Use-after-free fix
Date: Thu, 12 Apr 2018 11:10:26 -0600 [thread overview]
Message-ID: <20180412171025.GB6424@localhost.localdomain> (raw)
In-Reply-To: <a97b5921e5cf4855b5e76110a7984fdf@ausx13mps321.AMER.DELL.COM>
On Thu, Apr 12, 2018 at 05:06:05PM +0000, Alex_Gagniuc@Dellteam.com wrote:
> From: Keith Busch [mailto:keith.busch@intel.com]
>
> > AER error handling walks the PCI topology below a root port, saving
> > pointers of the pci_dev structs affected by the error along the way.
>
> Hi Keith,
>
> I've been trying to do an ABA test to confirm that your change
> eliminates the use-after-free issue we've seen. The race seems to be
> quite elusive, so I can't reliably reproduce it. Your changes have not
> been forgotten; I have them staged for further testing.
>
> Alex
No worries. This is essentially just a "safe" version of the patch that
you had tested, so if that one was successful, this one should be too.
next prev parent reply other threads:[~2018-04-12 17:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-09 22:04 [PATCH 0/4] PCI/AER: Use-after-free fix Keith Busch
2018-04-09 22:04 ` [PATCH 1/4] PCI/AER: Remove unused parameters Keith Busch
2018-04-09 22:04 ` [PATCH 2/4] PCI/AER: Replace struct pcie_device with pci_dev Keith Busch
2018-04-09 22:04 ` [PATCH 3/4] PCI/AER: Reference count aer structures Keith Busch
2018-04-09 22:04 ` [PATCH 4/4] PCI/AER: Lock pci topology when scanning errors Keith Busch
2018-06-05 22:09 ` Bjorn Helgaas
2018-06-05 22:18 ` Keith Busch
2018-06-06 13:52 ` Bjorn Helgaas
2018-04-10 13:15 ` [PATCH 0/4] PCI/AER: Use-after-free fix Dongdong Liu
2018-04-12 17:06 ` Alex_Gagniuc
2018-04-12 16:47 ` Scott Bauer
2018-04-13 14:49 ` Alex_Gagniuc
2018-04-16 19:49 ` Alex_Gagniuc
2018-04-12 17:10 ` Keith Busch [this message]
2018-06-05 22:11 ` 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=20180412171025.GB6424@localhost.localdomain \
--to=keith.busch@intel.com \
--cc=Alex_Gagniuc@Dellteam.com \
--cc=bhelgaas@google.com \
--cc=linux-pci@vger.kernel.org \
--cc=scott.bauer@intel.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;
as well as URLs for NNTP newsgroup(s).