From: patchwork-bot+netdevbpf@kernel.org
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, hangbin.liu@linux.dev, stable@vger.kernel.org
Subject: Re: [PATCH net v5 1/2] veth: keep carrier off when resizing channels with a down peer
Date: Mon, 02 Nov 2026 14:30:07 +0000 [thread overview]
Message-ID: <179362980730.4080032.15822012314713396959.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261029024259.3700-1-yana06070@163.com>
Hello:
This series was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Thu, 29 Oct 2026 10:42:58 +0800 you 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:
>
> [...]
Here is the summary with links:
- [net,v5,1/2] veth: keep carrier off when resizing channels with a down peer
https://git.kernel.org/netdev/net/c/2d0219177934
- [net,v5,2/2] selftests: net: check veth carrier after changing channel counts
https://git.kernel.org/netdev/net/c/c1f04ea0aa0f
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-11-02 14:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-29 2:42 [PATCH net v5 1/2] veth: keep carrier off when resizing channels with a down peer Xia Yan
2026-10-29 2:42 ` [PATCH net v5 2/2] selftests: net: check veth carrier after changing channel counts Xia Yan
2026-10-30 3:26 ` [PATCH net v5 1/2] veth: keep carrier off when resizing channels with a down peer Jiayuan Chen
2026-11-02 14:30 ` patchwork-bot+netdevbpf [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=179362980730.4080032.15822012314713396959.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=hangbin.liu@linux.dev \
--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