Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Simon Horman <horms@kernel.org>
To: Jamal Hadi Salim <jhs@mojatatu.com>
Cc: netdev@vger.kernel.org, owen@verialabs.com, jiri@resnulli.us,
	victor@mojatatu.com, davem@davemloft.net, edumazet@kernel.org,
	kuba@kernel.org, pabeni@redhat.com, sashiko-bot@kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH net v2 2/2] net/sched: sch_teql: fix use-after-free on lower qdisc drop
Date: Wed, 28 Oct 2026 14:27:06 +0000	[thread overview]
Message-ID: <20261028142706.GV257209@horms.kernel.org> (raw)
In-Reply-To: <CAM0EoM=53FJSOSFzO6sPuHqDi4wxNPxK_mYRBveUz_Y6ks9swg@mail.gmail.com>

On Tue, Oct 27, 2026 at 05:19:26PM -0400, Jamal Hadi Salim wrote:
> On Tue, Oct 27, 2026 at 2:29 PM Simon Horman <horms@kernel.org> wrote:
> >
> > This is an AI-generated review of your patch. The human sending this
> > email has considered the AI review valid, or at least plausible.
> > Full review at: https://netdev-ai.bots.linux.dev/sashiko/#/patchset/QDISC-Y0BY.v2.r0.20261024060625-1@mojatatu.com?part=2
> 
> So this email was stuck at sashiko because the email fields wouldnt
> allow it. Set at:
> email_status: Muted, smtp_enabled: false
> The same with patch 2/2

Fun times in AI-land.

> I will respond to both here. Summary is: i will not be sending an update.
> 
> For patch [1/2] net/sched: sch_teql: fix slaves_lock IRQ deadlock
> The High is pre-existing and not introduced by this patch, which only
> converts slaves_lock to a raw spinlock.
> I have a separate fix that bounds the walk by a slave_count maintained
> under slaves_lock; it will be posted after this  series gets merged.
> 
> Patch [2/2] net/sched: sch_teql: fix use-after-free on lower qdisc drop:
> 
> 1) Low: agreed, the changelog is misleading (the code is intended as written).
> NETDEV_TX_OK and NET_XMIT_CN are both counted as good transmits,
> matching  net_xmit_eval(); any other consumed result is charged to
> tx_dropped.
> I don't think it warrants a respin on its own unless something even
> semi-serious shows up in the code.
> 
> 2) Medium: the non-rotation is pre-existing.  Before this patch the
> drop path never advanced master->slaves either; it just retried the
> freed skb, which is the use-after-free being fixed.
> Advancing to NEXT_SLAVE(q) here is a  load-distribution improvement,
> not a correctness requirement of this fix.
>  IMO:   I would rather not inclued a policy change into the UAF fix; I
> can send it  separately.

Thanks for the feedback.
I agree with your suggested approaches.

Reviewed-by: Simon Horman <horms@kernel.org>


  reply	other threads:[~2026-10-28 14:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-24 14:34 [PATCH net v2 0/2] net/sched: sch_teql: fix transmit-path regressions Jamal Hadi Salim
2026-10-24 14:34 ` [PATCH net v2 1/2] net/sched: sch_teql: fix slaves_lock IRQ deadlock Jamal Hadi Salim
2026-10-24 14:34   ` [PATCH net v2 2/2] net/sched: sch_teql: fix use-after-free on lower qdisc drop Jamal Hadi Salim
2026-10-27 18:26     ` Simon Horman
2026-10-27 21:19       ` Jamal Hadi Salim
2026-10-28 14:27         ` Simon Horman [this message]
2026-10-28 14:27   ` [PATCH net v2 1/2] net/sched: sch_teql: fix slaves_lock IRQ deadlock Simon Horman
2026-10-24 14:36 ` [PATCH net v2 0/2] net/sched: sch_teql: fix transmit-path regressions netdev-bot+sinfo
2026-10-24 14:40   ` Jamal Hadi Salim
2026-10-29 10:40 ` patchwork-bot+netdevbpf

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=20261028142706.GV257209@horms.kernel.org \
    --to=horms@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@kernel.org \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=owen@verialabs.com \
    --cc=pabeni@redhat.com \
    --cc=sashiko-bot@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=victor@mojatatu.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