Netdev List
 help / color / mirror / Atom feed
From: netdev-bot+sashiko@kernel.org
To: mmc@linux.ibm.com
Cc: netdev@vger.kernel.org, nnac123@linux.ibm.com,
	maddy@linux.ibm.com, mpe@ellerman.id.au, npiggin@gmail.com,
	chleroy@kernel.org, ritesh.list@gmail.com, sshegde@linux.ibm.com,
	andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@kernel.org,
	kuba@kernel.org, pabeni@redhat.com,
	linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
	horms@kernel.org, davemarq@linux.ibm.com, bjking1@linux.ibm.com,
	brking@linux.vnet.ibm.com, tlfalcon@linux.vnet.ibm.com,
	jmaxwell37@gmail.com, zdai@us.ibm.com, marcelo.leitner@gmail.com,
	ksiva@linux.vnet.ibm.com
Subject: Re: [PATCH net-next v4 6/9] ibmveth: return the error when set_channels cannot add TX queues
Date: Tue, 13 Oct 2026 05:51:13 +0000	[thread overview]
Message-ID: <179187067343.434549.13620281833326474487@kernel.org> (raw)
In-Reply-To: <20261012050518.88858-7-mmc@linux.ibm.com>

Thank you for your contribution! Sashiko AI review found more severe
issue(s) in other patches of this series. This mail is only an FYI, in case
you want to address the nit picks below when you respin.

Low priority / nit picks for your consideration:

- [Low] The commit message for "ibmveth: return the error when
  set_channels cannot add TX queues" says the bug was "Found by AI-…

--

ibmveth: return the error when set_channels cannot add TX queues

If ibmveth_set_channels() fails to allocate a TX long term buffer for a
new queue, it falls back to the old queue count. The successful
netif_set_real_num_tx_queues() call then overwrote rc, so ethtool -L
reported success. This patch saves the allocation error in alloc_rc and
returns it when the fallback succeeds.

> Found by AI-assisted review of the ibmveth multi-queue RX series and
> confirmed by code inspection. Tested on a POWER10 LPAR with the TX
> buffer allocation forced to fail by a test-only module parameter (not
> part of this patch): ethtool -L tx 8 now fails with -ENOMEM and the
> device keeps its four queues and passes traffic. No kernel selftests
> cover ibmveth.
>
> Fixes: 10c2aba89cc0 ("ibmveth: Ethtool set queue support")
> Signed-off-by: Mingming Cao <mmc@linux.ibm.com>

[Severity: Low]
This isn't a bug, but should the trailer block carry an Assisted-by tag?

The message body says the bug was found by AI-assisted review. The
trailers only have Fixes: and Signed-off-by:.

Documentation/process/submitting-patches.rst, in "Using Assisted-by:",
says:

  If you used any sort of advanced coding tool in the creation of your
  patch, you need to acknowledge that use by adding an Assisted-by tag.
  Failure to do so may impede the acceptance of your work.

Documentation/process/coding-assistants.rst gives the format:

  Assisted-by: LLM [TOOL1] [TOOL2]

Step 6 of its "Procedure for finding and fixing bugs" section also says
a fix for an AI-found bug should add an Assisted-by tag.

Could an Assisted-by: trailer be added to this commit?

-- 
Sashiko AI review · https://netdev-ai.bots.linux.dev/sashiko/#/patchset/20261012050518.88858-1-mmc%40linux.ibm.com

  reply	other threads:[~2026-10-13  5:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-12  5:05 [PATCH net-next v4 0/9] ibmveth: fix hangs, use-after-frees and netpoll races Mingming Cao
2026-10-12  5:05 ` [PATCH net-next v4 1/9] ibmveth: fix netpoll races with RX replenish Mingming Cao
2026-10-12  5:05 ` [PATCH net-next v4 2/9] ibmveth: do not close twice after a failed reopen Mingming Cao
2026-10-12  5:05 ` [PATCH net-next v4 3/9] ibmveth: disable the reset work before unregister in remove Mingming Cao
2026-10-12  5:05 ` [PATCH net-next v4 4/9] ibmveth: step past bad RX correlators instead of spinning or oopsing Mingming Cao
2026-10-13  5:51   ` netdev-bot+sashiko
2026-10-12  5:05 ` [PATCH net-next v4 5/9] ibmveth: release the pool kobjects when probe fails Mingming Cao
2026-10-12  5:05 ` [PATCH net-next v4 6/9] ibmveth: return the error when set_channels cannot add TX queues Mingming Cao
2026-10-13  5:51   ` netdev-bot+sashiko [this message]
2026-10-12  5:05 ` [PATCH net-next v4 7/9] ibmveth: wait for in-flight transmits in ibmveth_close() Mingming Cao
2026-10-12  5:05 ` [PATCH net-next v4 8/9] ibmveth: wait for the RX poll to return before freeing the RX queue Mingming Cao
2026-10-12  5:05 ` [PATCH net-next v4 9/9] ibmveth: check headers in the RX large send and checksum helpers Mingming Cao
2026-10-13  5:51   ` netdev-bot+sashiko

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=179187067343.434549.13620281833326474487@kernel.org \
    --to=netdev-bot+sashiko@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=bjking1@linux.ibm.com \
    --cc=brking@linux.vnet.ibm.com \
    --cc=chleroy@kernel.org \
    --cc=davem@davemloft.net \
    --cc=davemarq@linux.ibm.com \
    --cc=edumazet@kernel.org \
    --cc=horms@kernel.org \
    --cc=jmaxwell37@gmail.com \
    --cc=ksiva@linux.vnet.ibm.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=maddy@linux.ibm.com \
    --cc=marcelo.leitner@gmail.com \
    --cc=mmc@linux.ibm.com \
    --cc=mpe@ellerman.id.au \
    --cc=netdev@vger.kernel.org \
    --cc=nnac123@linux.ibm.com \
    --cc=npiggin@gmail.com \
    --cc=pabeni@redhat.com \
    --cc=ritesh.list@gmail.com \
    --cc=sshegde@linux.ibm.com \
    --cc=tlfalcon@linux.vnet.ibm.com \
    --cc=zdai@us.ibm.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