mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Holger Hoffstätte" <holger@applied-asynchrony.com>
To: "Alan J. Wylie" <alan@wylie.me.uk>
Cc: "Jamal Hadi Salim" <jhs@mojatatu.com>,
	regressions@lists.linux.dev,
	"Cong Wang" <xiyou.wangcong@gmail.com>,
	"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: Tue, 22 Apr 2025 19:20:24 +0200	[thread overview]
Message-ID: <4e2a6522-d455-f0ce-c77d-b430c3047d7c@applied-asynchrony.com> (raw)
In-Reply-To: <20250422175145.1cb0bd98@frodo.int.wylie.me.uk>

(cc: Greg KH)

On 2025-04-22 18:51, Alan J. Wylie wrote:
> On Mon, 21 Apr 2025 21:09:27 +0100
> "Alan J. Wylie" <alan@wylie.me.uk> wrote:
> 
>> On Mon, 21 Apr 2025 21:47:44 +0200
>> Holger Hoffstätte <holger@applied-asynchrony.com> wrote:
>>
>>>> I'm afraid that didn't help. Same panic.
>>>
>>> Bummer :-(
>>>
>>> Might be something else missing then - so for now the only other
>>> thing I'd suggest is to revert the removal of the qlen check in
>>> fq_codel.
>>
>> Like this?
>>
>> $ git diff  sch_fq_codel.c
>> diff --git a/net/sched/sch_fq_codel.c b/net/sched/sch_fq_codel.c
>> index 6c9029f71e88..4fdf317b82ec 100644
>> --- a/net/sched/sch_fq_codel.c
>> +++ b/net/sched/sch_fq_codel.c
>> @@ -316,7 +316,7 @@ static struct sk_buff *fq_codel_dequeue(struct
>> Qdisc *sch) qdisc_bstats_update(sch, skb);
>>          flow->deficit -= qdisc_pkt_len(skb);
>>   
>> -       if (q->cstats.drop_count) {
>> +       if (q->cstats.drop_count && sch->q.qlen) {
>>                  qdisc_tree_reduce_backlog(sch, q->cstats.drop_count,
>>                                            q->cstats.drop_len);
>>                  q->cstats.drop_count = 0;
>> $
>>
> 
> It's been about 21 hours and no crash yet. I had an excellent day down
> a cave, so there's not been as much Internet traffic as usual, but
> there's a good chance the above patch as at least worked around, if not
> fixed the issue.

Thought so .. \o/

I guess now the question is what to do about it. IIUC the fix series [1]
addressed some kind of UAF problem, but obviously was not applied
correctly or is missing follow-ups. It's also a bit mysterious why
adding the HTB patch didn't work.

Maybe Cong Wang can advise what to do here?

So unless someone else has any ideas: Greg, please revert:

6.14.y/a57fe60ef4cf96bfbb6b58397ec28bdb5a5c6b31
("codel: remove sch->q.qlen check before qdisc_tree_reduce_backlog()")

and probably from 6.12 as well.

cheers
Holger

[1] https://lore.kernel.org/all/20250403211033.166059-1-xiyou.wangcong@gmail.com/

  reply	other threads:[~2025-04-22 17:20 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-21  9:40 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 [this message]
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
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=4e2a6522-d455-f0ce-c77d-b430c3047d7c@applied-asynchrony.com \
    --to=holger@applied-asynchrony.com \
    --cc=alan@wylie.me.uk \
    --cc=gregkh@linuxfoundation.org \
    --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 \
    --cc=xiyou.wangcong@gmail.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

all inboxes | Powered by JetHome®