From: Tang Yizhou <tangyeechou@gmail.com>
To: Cyril Hrubis <chrubis@suse.cz>,
Andrea Cervesato <andrea.cervesato@suse.com>
Cc: linuxtestproject.agent@gmail.com, ltp@lists.linux.it,
Hongtao Zhang <zhanghongtao35@huawei.com>
Subject: Re: [LTP] Revert "tpci: unbind driver in test_assign_resources()"
Date: Thu, 30 Jul 2026 17:04:41 +0800 [thread overview]
Message-ID: <77cf7e28-c8a4-4017-9ca7-425739d7378f@gmail.com> (raw)
In-Reply-To: <amsRGxrUfMnjDlFT@yuki.lan>
On 30/7/26 4:53 pm, Cyril Hrubis wrote:
> Hi!
>>> We recently confirmed this commit does cause a flood of I/O errors on
>>> the root filesystem in our testing, leaving the machine unusable until
>>> reboot.
>>>
>>> Given that, we'd appreciate the community helping to decide soon
>>> whether the revert is warranted.
>>
>> Are you 100% sure that is caused by the patch you want to revert?
>> Because the patch looked ok to me when I reviewed. We need to have
>> more context and info around the issue which has been generated in
>> order to avoid any workaround for a system/kernel bug.
>
> AFAIK the testing module grabs first device available on the system and
> uses it for testing. Which means that if you are unlucky it's your
> network card, or disk controller and you force reload it on a live
> system.
>
> And honestly the PCI test should be either rewritten and cleaned up to
> do something more sensible or just removed. As it is it's too fragile.
>
Thank you for your feedback. It is very helpful to us.
--
Best Regards,
Yi
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2026-07-30 9:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-14 9:06 [LTP] [PATCH] Revert "tpci: unbind driver in test_assign_resources()" Hongtao Zhang via ltp
2026-07-14 10:49 ` [LTP] " linuxtestproject.agent
2026-07-14 11:05 ` Yizhou Tang
2026-07-15 15:54 ` Andrea Cervesato via ltp
2026-07-16 2:43 ` Yizhou Tang
2026-07-30 8:53 ` Cyril Hrubis
2026-07-30 9:04 ` Tang Yizhou [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=77cf7e28-c8a4-4017-9ca7-425739d7378f@gmail.com \
--to=tangyeechou@gmail.com \
--cc=andrea.cervesato@suse.com \
--cc=chrubis@suse.cz \
--cc=linuxtestproject.agent@gmail.com \
--cc=ltp@lists.linux.it \
--cc=zhanghongtao35@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