From: Bjorn Helgaas <helgaas@kernel.org>
To: Jay Fang <f.fangjian@huawei.com>
Cc: linux-pci@vger.kernel.org, linuxarm@huawei.com
Subject: Re: [PATCH] PCI/AER: Fix AER/sysfs sriov_numvfs deadlock in pcie_do_recovery()
Date: Tue, 19 Nov 2019 13:52:05 -0600 [thread overview]
Message-ID: <20191119195205.GA210735@google.com> (raw)
In-Reply-To: <bdfaaa34-3d3d-ad9a-4e24-4be97e85d216@huawei.com>
On Tue, Nov 19, 2019 at 04:57:30PM +0800, Jay Fang wrote:
> On 2019/11/15 6:39, Bjorn Helgaas wrote:
> > On Fri, Sep 06, 2019 at 10:33:58AM +0800, Jay Fang wrote:
> >> A deadlock triggered by a NONFATAL AER event during a sysfs "sriov_numvfs"
> >> operation:
> >
> > How often does this happen? Always? Only when an AER event races
> > with the sysfs write?
> Although not very frequent,the impact is fatal. This bug is very
> necessary to be fixed.
Absolutely; I didn't mean to suggest that we shouldn't fix it. I only
wanted to know how to prioritize it against other issues.
Bjorn
prev parent reply other threads:[~2019-11-19 19:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-06 2:33 [PATCH] PCI/AER: Fix AER/sysfs sriov_numvfs deadlock in pcie_do_recovery() Jay Fang
2019-09-17 2:23 ` Jay Fang
2019-11-14 22:39 ` Bjorn Helgaas
2019-11-19 8:57 ` Jay Fang
2019-11-19 19:52 ` Bjorn Helgaas [this message]
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=20191119195205.GA210735@google.com \
--to=helgaas@kernel.org \
--cc=f.fangjian@huawei.com \
--cc=linux-pci@vger.kernel.org \
--cc=linuxarm@huawei.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).