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: Fri, 25 Apr 2025 09:08:29 -0700	[thread overview]
Message-ID: <aAuzfQe08tFJclNJ@pop-os.localdomain> (raw)
In-Reply-To: <20250424135331.02511131@frodo.int.wylie.me.uk>

On Thu, Apr 24, 2025 at 01:53:31PM +0100, Alan J. Wylie wrote:
> > On Tue, Apr 22, 2025 at 07:20:24PM +0200, Holger Hoffstätte wrote:
> 
> > Meanwhile, if you could provide a reliable (and ideally minimum)
> > reproducer, it would help me a lot to debug.
> 
> I've found a reproducer. Below is a stripped down version of the shell script
> that I posted in my initial report.
> 
> Running this in a 1 second loop is enough to cause the panic very quickly.
> 
> It seems a bit of network traffic is needed, too.

Excellent! Now I can try it on my side instead of bothering you. :)

I will check if applying all patches here could make crash and warning
go away. And of course, I need to really understand why the crash still
happened even after the qlen check adding to htb_qlen_notify(), which is
unexpected to me.

Thanks a lot!

  reply	other threads:[~2025-04-25 16:08 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 [this message]
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
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=aAuzfQe08tFJclNJ@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.