[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CABOYnLzNSp+ESUEtSFYfKbS=RS9XdQM=4uECpqbsdkTiv4scNg@mail.gmail.com>
Date: Sat, 9 Dec 2023 11:08:41 +0800
From: xingwei lee <xrivendell7@...il.com>
To: Thomas Gleixner <tglx@...utronix.de>
Cc: syzbot+f2c4e7bfcca6c6d6324c@...kaller.appspotmail.com,
jstultz@...gle.com, linux-kernel@...r.kernel.org, sboyd@...nel.org,
syzkaller-bugs@...glegroups.com
Subject: Re: [syzbot] [kernel?] possible deadlock in alarm_handle_timer
Hello, tglx.
I reprduce this bug with
linux-next commit:
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/log/?id=eff99d8edbed7918317331ebd1e365d8e955d65e
kernel config: https://syzkaller.appspot.com/text?tag=KernelConfig&x=61991b2630c19677
the same configuration as the syzbot dashboard:
https://syzkaller.appspot.com/bug?extid=f2c4e7bfcca6c6d6324c.
However, I do not entangled the information and just try to generate
repro.c with the configuration provided by syzbot dashboard.
When I try the repro.c in the lasted upstream commit:
f2e8a57ee9036c7d5443382b6c3c09b51a92ec7e, it can't crash the kernel at
all. Should I assume this bug was fixed by the mainline?
Thanks!
Best Regards
xingwei Lee
Thomas Gleixner <tglx@...utronix.de> 于2023年12月9日周六 05:42写道:
>
> On Tue, Dec 05 2023 at 10:07, xingwei lee wrote:
> > Hello
> > I reproduced this bug with repro.c
>
> Which bug?
>
> What happens if you run this and what's the potential deadlock?
>
> Lot's of information missing here including the kernel version ...
>
> Thanks,
>
> tglx
Powered by blists - more mailing lists