From: Hangbin Liu <hangbin.liu@linux.dev>
To: Xia Yan <yana06070@163.com>
Cc: netdev@vger.kernel.org, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@kernel.org, horms@kernel.org,
kuba@kernel.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org, pabeni@redhat.com,
shuah@kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH net v3 1/2] veth: keep carrier off when resizing channels with a down peer
Date: Fri, 23 Oct 2026 09:56:32 +0800 [thread overview]
Message-ID: <atq-0HbV71AcQi5t@fedora> (raw)
In-Reply-To: <20261022085842.2527-1-yana06070@163.com>
On Thu, Oct 22, 2026 at 04:58:41PM +0800, Xia Yan wrote:
> veth_set_channels() temporarily turns carrier off while reconfiguring a
> running interface. It then turns carrier on for both ends without
> checking whether the peer is administratively up. If only one end is up,
> changing its channel counts therefore reports LOWER_UP even though the
> peer remains down.
>
> For example, after creating a pair with two RX and TX queues per end:
>
> ip link set vca up
> ethtool -L vca rx 1 tx 1
>
> vca incorrectly reports LOWER_UP while vcb is still down.
>
> Only restore carrier when the peer has IFF_UP, matching veth_open().
> The local interface is already known to be running at this point.
>
> Found during LLM-assisted source review and reproduced with a veth pair
> in network namespaces, without kernel instrumentation or error injection.
> With the complete default veth.sh on x86_64 QEMU/KVM (three vCPUs), the
> four mixed up/down cases fail before the fix and all six carrier cases
> pass after it. All 55 existing checks pass on both kernels.
>
> Fixes: 4752eeb3d891 ("veth: implement support for set_channel ethtool op")
> Cc: stable@vger.kernel.org
> Assisted-by: LLM
> Signed-off-by: Xia Yan <yana06070@163.com>
> ---
>
> Notes:
> Changes in v3:
> - Driver code is unchanged from v2.
> - The companion selftest is now part of veth.sh.
>
> v2: https://lore.kernel.org/netdev/20261020135544.24441-1-yana06070@163.com/
>
> Testing on the v2 baseline 513444cc62e2:
> - Complete default veth.sh on x86_64 QEMU/KVM, three vCPUs:
> before: 57 checks pass, four mixed up/down carrier checks fail;
> after: all 61 checks pass. The 55 existing checks pass on both.
> - bash -n and git diff --check pass.
> - If creating the veth pair fails, the case is skipped without
> masking failures from earlier test cases.
>
> Both patches also apply to net/main ffdf678dd166
> (application check only, checked on 2026-10-22).
>
> The QEMU guests failed to power off cleanly (initramfs issue) after
> the tests completed; the exit codes above are the veth.sh results.
>
>
> drivers/net/veth.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/net/veth.c b/drivers/net/veth.c
> index 643b97d..4e75830 100644
> --- a/drivers/net/veth.c
> +++ b/drivers/net/veth.c
> @@ -1372,9 +1372,10 @@ static int veth_set_channels(struct net_device *dev,
> * to identify the range we have to disable
> */
> veth_disable_range_safe(dev, new_rx_count, old_rx_count);
> - netif_carrier_on(dev);
> - if (peer)
> + if (peer && (peer->flags & IFF_UP)) {
> + netif_carrier_on(dev);
> netif_carrier_on(peer);
> + }
> }
>
> /* update XDP supported features */
>
> base-commit: 513444cc62e231a11c9b15ea88de0890da9b2b4f
> --
> 2.43.0
>
This one looks good to me. I can reproduce the report issue.
Reviewed-by: Hangbin Liu <liuhangbin@kylinos.cn>
prev parent reply other threads:[~2026-10-23 1:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-22 8:58 Xia Yan
2026-10-22 8:58 ` [PATCH net v3 2/2] selftests: net: check veth carrier after changing channel counts Xia Yan
2026-10-23 1:47 ` Hangbin Liu
2026-10-23 2:33 ` Xia Yan
2026-10-23 3:15 ` Hangbin Liu
2026-10-23 3:35 ` Xia Yan
2026-10-23 1:56 ` Hangbin Liu [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=atq-0HbV71AcQi5t@fedora \
--to=hangbin.liu@linux.dev \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
--cc=stable@vger.kernel.org \
--cc=yana06070@163.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
all inboxes | Powered by JetHome®