From: patchwork-bot+netdevbpf@kernel.org
To: Umang Pokhriyal <umangpokhriyall@gmail.com>
Cc: netdev@vger.kernel.org, willemdebruijn.kernel@gmail.com,
jasowangio@gmail.com, andrew+netdev@lunn.ch, davem@davemloft.net,
edumazet@kernel.org, kuba@kernel.org, pabeni@redhat.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] tun: don't steer a flow to a queue index that no longer exists
Date: Thu, 19 Nov 2026 11:40:05 +0000 [thread overview]
Message-ID: <179508840503.3038224.16974538898248760446.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261114153617.102288-1-umangpokhriyall@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Sat, 14 Nov 2026 21:06:17 +0530 you wrote:
> A multi-queue tun device keeps a flow table that maps each flow to the
> index of the queue it last used, so that packets sent back to the flow
> go to the same queue. When a queue is removed, the last queue moves
> into its index. An entry that still holds the last queue's old index
> then holds an index that no longer exists. Packets of that flow are
> sent to queue 0 with a "selects TX queue" warning, until the flow sends
> again or its entry expires after a few seconds.
>
> [...]
Here is the summary with links:
- [net-next] tun: don't steer a flow to a queue index that no longer exists
https://git.kernel.org/netdev/net-next/c/9068e05d35f3
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-19 11:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-14 15:36 Umang Pokhriyal
2026-11-19 11:40 ` 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=179508840503.3038224.16974538898248760446.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=jasowangio@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=umangpokhriyall@gmail.com \
--cc=willemdebruijn.kernel@gmail.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®