From: "Fangjian (Turing)" <f.fangjian@huawei.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: <linux-pci@vger.kernel.org>, "Rafael J. Wysocki" <rjw@rjwysocki.net>
Subject: Re: Bug report: AER driver deadlock
Date: Mon, 5 Aug 2019 20:43:42 +0800 [thread overview]
Message-ID: <7b181647-3158-2a79-c6ca-d81056625fc8@huawei.com> (raw)
In-Reply-To: <20190625171639.GA103694@google.com>
Kindly Ping...
Best Regards,
Jay
On 2019/6/26 1:16, Bjorn Helgaas wrote:
> On Tue, Jun 04, 2019 at 11:25:44AM +0800, Fangjian (Turing) wrote:
>> Hi, We met a deadlock triggered by a NONFATAL AER event during a sysfs
>> "sriov_numvfs" operation. Any suggestion to fix such deadlock ?
>
> Here's a bugzilla report for this; please reference it and this email
> thread in any patches to fix it:
>
> https://bugzilla.kernel.org/show_bug.cgi?id=203981
>
> .
>
next prev parent reply other threads:[~2019-08-05 12:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-04 3:25 Bug report: AER driver deadlock Fangjian (Turing)
2019-06-04 14:34 ` Sinan Kaya
2019-06-04 23:47 ` Benjamin Herrenschmidt
2019-06-05 0:59 ` Sinan Kaya
2019-06-20 3:14 ` Fangjian (Turing)
2019-06-25 17:16 ` Bjorn Helgaas
2019-08-05 12:43 ` Fangjian (Turing) [this message]
2019-08-16 7:11 ` Jay Fang
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=7b181647-3158-2a79-c6ca-d81056625fc8@huawei.com \
--to=f.fangjian@huawei.com \
--cc=helgaas@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=rjw@rjwysocki.net \
/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).