All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Jamal Hadi Salim <jhs@mojatatu.com>
Cc: netdev@vger.kernel.org, victor@mojatatu.com, jiri@resnulli.us,
	davem@davemloft.net, edumazet@kernel.org, kuba@kernel.org,
	pabeni@redhat.com, vinicius.gomes@intel.com, horms@kernel.org,
	hawk@kernel.org, daniel@iogearbox.net, sashiko-bot@kernel.org,
	bpf@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH net v6] net/sched: clamp skb->queue_mapping before indexing the tx queue
Date: Tue, 03 Nov 2026 21:40:04 +0000	[thread overview]
Message-ID: <179374200480.1894115.5049965810872091350.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <QDISC-MD1X.v6.r0.20261029162633-1@mojatatu.com>

Hello:

This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:

On Thu, 29 Oct 2026 16:36:31 -0400 you wrote:
> This issue was caught by Sashiko (nipa). A producer-side path cap is
> already merged (ea4d4b5dddb5); this patch adds the matching consumer-side
> caps.
> 
> The issue:
> The tx queue is picked and capped in netdev_core_pick_tx() before the
> __dev_xmit_skb() qdisc enqueue path. A tc BPF program running inside an
> egress qdisc (not clsact) can then change __sk_buff->queue_mapping; that
> store is never re-checked. bpf_convert_ctx_access() bounds it only by
> NO_QUEUE_MAPPING, not by the device's queue count.
> 
> [...]

Here is the summary with links:
  - [net,v6] net/sched: clamp skb->queue_mapping before indexing the tx queue
    https://git.kernel.org/netdev/net/c/f19f2b308beb

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-11-03 21:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-29 20:36 [PATCH net v6] net/sched: clamp skb->queue_mapping before indexing the tx queue Jamal Hadi Salim
2026-11-03 10:50 ` Simon Horman
2026-11-03 10:58   ` Jamal Hadi Salim
2026-11-03 21: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=179374200480.1894115.5049965810872091350.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@kernel.org \
    --cc=hawk@kernel.org \
    --cc=horms@kernel.org \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sashiko-bot@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=victor@mojatatu.com \
    --cc=vinicius.gomes@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.