All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cong Wang <xiyou.wangcong@gmail.com>
To: "Alan J. Wylie" <alan@wylie.me.uk>
Cc: "Holger Hoffstätte" <holger@applied-asynchrony.com>,
	"Jamal Hadi Salim" <jhs@mojatatu.com>,
	regressions@lists.linux.dev, "Jiri Pirko" <jiri@resnulli.us>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Octavian Purdila" <tavip@google.com>,
	"Toke Høiland-Jørgensen" <toke@redhat.com>,
	stable@vger.kernel.org, "Greg KH" <gregkh@linuxfoundation.org>
Subject: Re: [REGRESSION] 6.14.3 panic - kernel NULL pointer dereference in htb_dequeue
Date: Mon, 28 Apr 2025 16:59:36 -0700	[thread overview]
Message-ID: <aBAWaAubkkTH9FAK@pop-os.localdomain> (raw)
In-Reply-To: <20250428223436.48529979@frodo.int.wylie.me.uk>

On Mon, Apr 28, 2025 at 10:34:36PM +0100, Alan J. Wylie wrote:
> On Mon, 28 Apr 2025 14:02:20 -0700
> Cong Wang <xiyou.wangcong@gmail.com> wrote:
> 
> > I doubt it is related to iptables. I will try some TCP traffic on my
> > side later, but I suspect this is related to the type of packets.
> > 
> > Meanwhile, since I still can't reproduce it here, do you mind applying
> > both of my patches on top of -net and test again?
> > 
[...] 
> 
> With those patches applied, I've run 5 or 6 SpeedTests, no panics.
> 
> There's several WARNINGS in the log, though, about one per run.

My bad, acctually I reproducced it with iperf (TCP traffic) using your
reproducer. I saw the warning/crash within 10 seconds. With the fix I
sent out, I didn't see any after ~10 mininutes, so it should be working 
probably.

Thanks!

  reply	other threads:[~2025-04-28 23:59 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-21  9:40 [REGRESSION] 6.14.3 panic - kernel NULL pointer dereference in htb_dequeue Alan J. Wylie
2025-04-21 11:50 ` Holger Hoffstätte
2025-04-21 12:10   ` Alan J. Wylie
2025-04-21 19:06     ` Alan J. Wylie
2025-04-21 19:47       ` Holger Hoffstätte
2025-04-21 20:09         ` Alan J. Wylie
2025-04-22 16:51           ` Alan J. Wylie
2025-04-22 17:20             ` Holger Hoffstätte
2025-04-22 20:42               ` Cong Wang
2025-04-22 20:47                 ` Alan J. Wylie
2025-04-22 21:49                   ` Cong Wang
2025-04-23  9:51                     ` Alan J. Wylie
2025-04-23 19:32                       ` Cong Wang
2025-04-24  6:53                         ` Alan J. Wylie
2025-04-24 12:53                         ` Alan J. Wylie
2025-04-25 16:08                           ` Cong Wang
2025-04-27 19:11                           ` Cong Wang
2025-04-27 19:42                             ` Alan J. Wylie
2025-04-27 20:35                               ` Alan J. Wylie
2025-04-28 21:02                                 ` Cong Wang
2025-04-28 21:34                                   ` Alan J. Wylie
2025-04-28 23:59                                     ` Cong Wang [this message]
2025-04-28 11:45               ` Greg KH
2025-04-28 12:28                 ` Holger Hoffstätte
2025-04-28 23:38                 ` Cong Wang

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=aBAWaAubkkTH9FAK@pop-os.localdomain \
    --to=xiyou.wangcong@gmail.com \
    --cc=alan@wylie.me.uk \
    --cc=gregkh@linuxfoundation.org \
    --cc=holger@applied-asynchrony.com \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=regressions@lists.linux.dev \
    --cc=stable@vger.kernel.org \
    --cc=tavip@google.com \
    --cc=toke@redhat.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.