From: LeoLiu-oc <LeoLiu-oc@zhaoxin.com>
To: Lukas Wunner <lukas@wunner.de>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
Mahesh J Salgaonkar <mahesh@linux.ibm.com>,
Przemek Kitszel <przemyslaw.kitszel@intel.com>,
Oliver O'Halloran <oohall@gmail.com>,
<linuxppc-dev@lists.ozlabs.org>, <linux-pci@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <CobeChen@zhaoxin.com>,
<ErosZhang@zhaoxin.com>, <TonyWWang@zhaoxin.com>
Subject: Re: [PATCH v2] PCI: dpc: Increase pciehp waiting time for DPC recovery
Date: Fri, 6 Feb 2026 19:07:50 +0800 [thread overview]
Message-ID: <c1c24812-37aa-48af-922f-2e43c659703c@zhaoxin.com> (raw)
In-Reply-To: <aYRatwSvUG0yQkHd@wunner.de>
在 2026/2/5 16:54, Lukas Wunner 写道:
>
>
> [这封邮件来自外部发件人 谨防风险]
>
> On Wed, Feb 04, 2026 at 11:55:42AM +0800, LeoLiu-oc wrote:
>> For example, The execution of the ice_pci_err_detected() in the ice network
>> card driver exceeded the maximum waiting time for DPC recovery, causing the
>> pciehp_disable_slot() to be executed which is not needed. From the user's
>> point of view, you will see that the ice network card may not be usable and
>> could even cause more serious errors, such as a kernel panic. kernel panic
>> is caused by a race between pciehp_disable_slot() and pcie_do_recovery().
>> In practice, we would observe that the ice network card is in an
>> unavailable state and a kernel panic.
>
> Unfortunately v2 was submitted without answering all of the questions
> and testing all of the things asked for during review:
>
> https://lore.kernel.org/all/aYBoP-B2E9fp_4YZ@wunner.de/
I have already replied to your concern in the following email. Please
pay attention to check it
https://lore.kernel.org/all/018007dd-68d9-4e16-b605-15d9c77ea13f@zhaoxin.com/
Yours sincerely,
LeoLiu-oc
prev parent reply other threads:[~2026-02-09 1:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-04 3:55 [PATCH v2] PCI: dpc: Increase pciehp waiting time for DPC recovery LeoLiu-oc
2026-02-05 8:54 ` Lukas Wunner
2026-02-06 11:07 ` LeoLiu-oc [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=c1c24812-37aa-48af-922f-2e43c659703c@zhaoxin.com \
--to=leoliu-oc@zhaoxin.com \
--cc=CobeChen@zhaoxin.com \
--cc=ErosZhang@zhaoxin.com \
--cc=TonyWWang@zhaoxin.com \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lukas@wunner.de \
--cc=mahesh@linux.ibm.com \
--cc=oohall@gmail.com \
--cc=przemyslaw.kitszel@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