linux-kernel - Re: WARNING: CPU: 0 PID: 1935 at kernel/timer.c:1621 migrate_timer

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <CAKohpokStOgdO-KFn8hcyV+neaNCvHLSG9od=qyi2-4rV62DRw@mail.gmail.com>
Date:	Sat, 5 Apr 2014 11:56:48 +0530
From:	Viresh Kumar <viresh.kumar@...aro.org>
To:	Jet Chen <jet.chen@...el.com>
Cc:	Thomas Gleixner <tglx@...utronix.de>,
	Fengguang Wu <fengguang.wu@...el.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: WARNING: CPU: 0 PID: 1935 at kernel/timer.c:1621 migrate_timer_list()

On 5 April 2014 10:00, Jet Chen <jet.chen@...el.com> wrote:
> vmlinuz from our build system doesn't have debug information. It is hard to
> use objdump to identify which routine is timer->function.

I see...

> But after several times trials, I get below dmesg messages.
> It is clear to see address of "timer->function" is 0xffffffff810d7010.
> In calling stack, " [<ffffffff810d7010>] ?
> clocksource_watchdog_kthread+0x40/0x40 ". So I guess timer->function is
> clocksource_watchdog_kthread.

Hmm.. not exactly this function as this isn't timer->function for any timer.
But I think I have found the right function with this hint:
clocksource_watchdog()

Can you please try to test the attached patch, which must fix it.
Untested. I will
then post it with your Tested-by :)

--
viresh

View attachment "0001-clocksource-register-cpu-notifier-to-remove-timer-fr.patch" of type "text/x-patch" (6108 bytes)