From: Thomas Gleixner <tglx@linutronix.de>
To: Will Deacon <will@kernel.org>
Cc: syzbot <syzbot+558f67d44ad7f098a3de@syzkaller.appspotmail.com>,
anna-maria@linutronix.de, frederic@kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
Catalin Marinas <catalin.marinas@arm.com>
Subject: Re: [syzbot] [kernel?] BUG: unable to handle kernel NULL pointer dereference in __hrtimer_run_queues
Date: Tue, 04 Jun 2024 18:10:04 +0200 [thread overview]
Message-ID: <87mso0665f.ffs@tglx> (raw)
In-Reply-To: <20240604133448.GB20384@willie-the-truck>
Will!
On Tue, Jun 04 2024 at 14:34, Will Deacon wrote:
> On Tue, Jun 04, 2024 at 02:29:57PM +0200, Thomas Gleixner wrote:
>> On Mon, Jun 03 2024 at 03:22, syzbot wrote:
>> > * 10: f9400821 ldr x1, [x1, #16] <-- trapping instruction
>> while (node->rb_left)
>>
>> > x2 : ff7000007f8cf8e8 x1 : 0000000000000080 x0 : 0000000000000080
>>
>> which obviously crashes. Now the question is how does the original node
>> end up with node::rb_right == 0x80?
>>
>> I doubt that this is a hrtimer or rbtree problem. It smells like random
>> data corruption caused by whatever. It might not even be an ARM64
>> specific issue though the C repro does not trigger on x86...
>>
>> Handing it over to Catalin and Will.
>
> I suspect this is a duplicate of:
>
> https://lore.kernel.org/lkml/20240604110119.GA20284@willie-the-truck/
>
> and there's a fix queued in the -mm tree.
That looks very much so.
Thanks,
tglx
next prev parent reply other threads:[~2024-06-04 16:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-03 10:22 [syzbot] [kernel?] BUG: unable to handle kernel NULL pointer dereference in __hrtimer_run_queues syzbot
2024-06-03 11:04 ` Hillf Danton
2024-06-04 12:29 ` Thomas Gleixner
2024-06-04 13:34 ` Will Deacon
2024-06-04 16:10 ` Thomas Gleixner [this message]
2024-06-04 12:45 ` Hillf Danton
2024-06-04 13:30 ` syzbot
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=87mso0665f.ffs@tglx \
--to=tglx@linutronix.de \
--cc=anna-maria@linutronix.de \
--cc=catalin.marinas@arm.com \
--cc=frederic@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+558f67d44ad7f098a3de@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=will@kernel.org \
/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