linux-kernel - Re: [RFC] panic on cascade() of kernel/time/timer.c

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <a4ebb733-b551-e88d-0ade-e08e7b7e49eb@huawei.com>
Date:   Wed, 30 Nov 2016 17:42:57 +0800
From:   Yisheng Xie <xieyisheng1@...wei.com>
To:     Thomas Gleixner <tglx@...utronix.de>
CC:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        John Stultz <john.stultz@...aro.org>,
        Hanjun Guo <guohanjun@...wei.com>,
        Xishi Qiu <qiuxishi@...wei.com>
Subject: Re: [RFC] panic on cascade() of kernel/time/timer.c



On 2016/11/30 17:18, Thomas Gleixner wrote:
> On Wed, 30 Nov 2016, Yisheng Xie wrote:
> 
>> Hi all,
>> The kernel version is 4.1.18, and we got a panic at cascade().
>> from the log it seems cause by BUG_ON of kernel/time/timer.c:1120.
>> Any ideas about about it?
> 
> Probably a timer which got freed while enqueued or some other wreckage in
> that area. Certainly not a core code problem.
> 
> Enable CONFIG_DEBUG_OBJECTS* and try to reproduce. The debug facility will
> tell you which driver/whatever causes the problem.
> 
Hi tglx,
Thank you for your suggestion, and we will do that test.

Thanks,
Yisheng Xie
> Thanks,
> 
> 	tglx
> 
> 
> .
>