mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: Linkui Xiao <xiaolinkui@126.com>, <netdev-bot+sinfo@kernel.org>
Cc: <przemyslaw.kitszel@intel.com>, <andrew+netdev@lunn.ch>,
	<davem@davemloft.net>, <edumazet@google.com>, <kuba@kernel.org>,
	<pabeni@redhat.com>, <intel-wired-lan@lists.osuosl.org>,
	<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	Linkui Xiao <xiaolinkui@kylinos.cn>, <stable@vger.kernel.org>
Subject: Re: [PATCH iwl-net v2 1/2] ice: detach the VF representor when ice_start_vfs() fails
Date: Tue, 29 Sep 2026 11:11:00 -0700	[thread overview]
Message-ID: <547ed917-77fc-4670-974c-4d4fd6fbf3e7@intel.com> (raw)
In-Reply-To: <d3f4ae98-3340-414b-9bd0-9f4588810821@126.com>



On 9/28/2026 12:14 AM, Linkui Xiao wrote:
> Hi,
> 
> Thanks for the review. Please find the missing information below.
> 
> - How the issue was discovered:
>    Found during manual code inspection of the ice VF setup/teardown 
> error paths. It was not reported by syzbot, a static analysis tool, or 
> an LLM scan, and was not hit in production.
> 
> - Whether the issue was actually triggered:
>    Not actually triggered. It is a theoretical error-path cleanup issue 
> found by inspection; no stack trace or error message was observed.
> 
> - Hardware tested:
>    Not tested on real hardware. The change was only compile-tested; no 
> affected Intel NIC/firmware test was performed.
> 
> The same applies to patch 2/2: it was also found by the same manual code 
> inspection, was not triggered at runtime, and was only compile-tested, 
> not tested on real hardware.
> 
> If a v3 is needed for other review reasons, I will include this 
> information in the commit messages.
> 
> Thanks,
> Linkui Xiao
> 
> On 2026/9/28 14:59, netdev-bot+sinfo@kernel.org wrote:
>> Hi!
>>
>> This is an automated message. This series looks like a fix, but its
>> commit messages seem to be missing some information:
>>
>>   - How the issue was discovered, e.g. hit in production, hit during
>>     development, syzbot report, manual code inspection, LLM or static
>>     analysis tool scan.
>>
>>   - Whether the issue was actually triggered, or is only theoretical
>>     (e.g. found by code inspection). If it was triggered please include
>>     the symptoms, like the stack trace or error messages.
>>
>>   - What hardware the change was tested on. For driver fixes please
>>     mention the device (and if relevant firmware version) used for
>>     testing, or say that the change was not tested on real hardware.
>>
>> Please do not repost the series just to address the above. Instead,
>> reply to this email with the missing information, so that reviewers
>> can take it into account. If the series needs another revision for
>> other reasons, please include the information in the commit messages
>> then.

Hi Jakub,

For patches that go through iwl-net, how did you want this handled? It 
says to not repost just to address the above, but since this will get 
submitted later, did you want the commit updated to make the latter 
check happy, did you want me to copy/paste the response to the commit, 
or something else?

Thanks,
Tony

>> The evaluation is done by an LLM so it may be wrong, if you think
>> that is the case please reply and explain.
> 


  reply	other threads:[~2026-09-29 18:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-28  6:53 Linkui Xiao
2026-09-28  6:53 ` [PATCH iwl-net v2 2/2] ice: release the VF MSI-X window " Linkui Xiao
2026-09-28 13:08   ` Tomasz Lichwala
2026-09-29  0:55     ` Linkui Xiao
2026-09-28 15:16   ` Loktionov, Aleksandr
2026-09-28  6:59 ` [PATCH iwl-net v2 1/2] ice: detach the VF representor " netdev-bot+sinfo
2026-09-28  7:14   ` Linkui Xiao
2026-09-29 18:11     ` Tony Nguyen [this message]
2026-09-28 13:08 ` Tomasz Lichwala
2026-09-28 15:16 ` Loktionov, Aleksandr

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=547ed917-77fc-4670-974c-4d4fd6fbf3e7@intel.com \
    --to=anthony.l.nguyen@intel.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev-bot+sinfo@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=przemyslaw.kitszel@intel.com \
    --cc=stable@vger.kernel.org \
    --cc=xiaolinkui@126.com \
    --cc=xiaolinkui@kylinos.cn \
    /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

all inboxes | Powered by JetHome®