public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Cong Wang <xiyou.wangcong@gmail.com>
To: Mingi Cho <mgcho.minic@gmail.com>
Cc: netdev@vger.kernel.org, jhs@mojatatu.com, jiri@resnulli.us,
	 mincho@theori.io, victor@mojatatu.com
Subject: Re: [RFC Patch net-next 0/2] net_sched: Move GSO segmentation to root qdisc
Date: Thu, 12 Mar 2026 12:55:11 -0700	[thread overview]
Message-ID: <CAM_iQpVcBEgLDDw=p440dTcXs7QC653V488gL76dsgrhv1EKmw@mail.gmail.com> (raw)
In-Reply-To: <20260312165757.GA3411905@mingi>

On Thu, Mar 12, 2026 at 9:58 AM Mingi Cho <mgcho.minic@gmail.com> wrote:
> Hi Cong,
>
> I tested the proposed patch and found that the reported bug was fixed. A qlen mismatch between Qdiscs can potentially cause UAF, so I believe this patch needs to be applied.
>
> When executing the PoC on the latest kernel without the patch applied, a warning message occurs in drr_dequeue() as shown below.

Hi Mingi,

Thanks for testing.

I quit my maintainer role and TC is none of my business any more.
Please contact other maintainers.

Regards,
Cong Wang

  reply	other threads:[~2026-03-12 19:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-01 23:29 [RFC Patch net-next 0/2] net_sched: Move GSO segmentation to root qdisc Cong Wang
2025-07-01 23:29 ` [RFC Patch net-next 1/2] " Cong Wang
2025-07-01 23:29 ` [RFC Patch net-next 2/2] net_sched: Propagate per-qdisc max_segment_size for GSO segmentation Cong Wang
2026-03-12 16:57 ` [RFC Patch net-next 0/2] net_sched: Move GSO segmentation to root qdisc Mingi Cho
2026-03-12 19:55   ` Cong Wang [this message]
2026-03-12 20:21   ` Jamal Hadi Salim
2026-03-13 13:38     ` Mingi Cho
2026-03-13 19:23       ` Jamal Hadi Salim
2026-03-26 10:29         ` Mingi Cho

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='CAM_iQpVcBEgLDDw=p440dTcXs7QC653V488gL76dsgrhv1EKmw@mail.gmail.com' \
    --to=xiyou.wangcong@gmail.com \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=mgcho.minic@gmail.com \
    --cc=mincho@theori.io \
    --cc=netdev@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