Linux Test Project
 help / color / mirror / Atom feed
From: linuxtestproject.agent@gmail.com
To: Andrea Cervesato <andrea.cervesato@suse.de>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] tpci: refactor kernel module
Date: Wed,  5 Aug 2026 10:38:21 +0000	[thread overview]
Message-ID: <20260805103821.8953-1-linuxtestproject.agent@gmail.com> (raw)
In-Reply-To: <20260805-tpci_refactoring-v1-1-4ca8d84f8a95@suse.com>

Hi Andrea,

On Wed, 5 Aug 2026, Andrea Cervesato wrote:
> tpci: refactor kernel module

--- [PATCH 2/2] ---

> tcpi: refactor test using new API

Low: Could "tcpi" be corrected to "tpci" so that the subject names the
component changed by the patch?

> 	for (int i = 0; i < PCI_TCASES_NUM; ++i) {
> 		if (!is_target && is_destructive_test(i))
> 			continue;

High: Could PCI_DISABLE remain excluded from this automatic sequence until
the module can detach the normal driver and restore the original device
state?

This path calls pci_release_regions() while that driver is still bound,
although the kernel API requires all region use to have ceased. No later
path requests those regions again. In addition, Linux 7.2
pci_disable_device() only disables bus mastering; it does not move
current_state to D3hot or D3cold. Consequently, an ordinary D0 target both
reports TFAIL and may be left without its driver's resource reservations.

> 	if (!devices_found)
> 		tst_brk(TCONF, "no PCI device found on the system");

Medium: Could the test separately track whether target_bus/target_devfn was
selected when -d is supplied?

If that BDF is absent or has no driver, its selection returns ENODEV, but
devices_found can still be nonzero because of other devices. The run then
passes after executing only safe cases, without reporting that none of the
requested destructive cases ran.

Verdict - Needs revision

---
Note:

The agent can sometimes produce false positives although often its
findings are genuine. If you find issues with the review, please
comment this email or ignore the suggestions.

Regards,
LTP AI Reviewer

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2026-08-05 10:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-05  9:44 [LTP] [PATCH 0/2] tcpi refactoring Andrea Cervesato
2026-08-05  9:44 ` [LTP] [PATCH 1/2] tpci: refactor kernel module Andrea Cervesato
2026-08-05 10:38   ` linuxtestproject.agent [this message]
2026-08-05  9:44 ` [LTP] [PATCH 2/2] tcpi: refactor test using new API Andrea Cervesato
  -- strict thread matches above, loose matches on Subject: below --
2026-08-06  8:10 [LTP] [PATCH v2 1/2] tpci: refactor kernel module Andrea Cervesato
2026-08-06 10:40 ` [LTP] " linuxtestproject.agent

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=20260805103821.8953-1-linuxtestproject.agent@gmail.com \
    --to=linuxtestproject.agent@gmail.com \
    --cc=andrea.cervesato@suse.de \
    --cc=ltp@lists.linux.it \
    /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