On 11/18/26 4:07 PM, [email protected] wrote:
Hi!

This is an automated message. This series looks like a fix, but its
commit messages seem to be missing some information:

  - Whether the issue was actually triggered, or is only theoretical
    (e.g. found by LLM and not proven at runtime). If it was triggered
    please include the symptoms, like the stack trace or kernel messages.

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.
Thanks.

Some of this context was included in the cover letter, but for reviewers'
convenience:

Both issues were identified during development and review of the ibmveth
multi-queue work. Patch 1 addresses a race when TX queues are reduced via
ethtool -L while traffic is running. Patch 2 addresses a race where a queued
reset can reopen a device that has already been administratively brought down.

I could not reproduce either issue directly. The fixes are based on analysis of
the existing code paths and rare race conditions. I exercised the affected
scenarios on a PowerVM LPAR, including TX queue reduction under traffic,
ifdown/up during iperf3 traffic, and queued reset testing while the device was
being brought down, and observed no regressions with the proposed fixes.

Thanks,
Mingming

Reply via email to