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: <CAKohpon+THY2NXEEOcWRbmrpfQUZYbHfO+Lw=D9TaJWk+_-J2g@mail.gmail.com>
Date:	Fri, 4 Apr 2014 13:22:28 +0530
From:	Viresh Kumar <viresh.kumar@...aro.org>
To:	Jet Chen <jet.chen@...el.com>
Cc:	Fengguang Wu <fengguang.wu@...el.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	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 4 April 2014 13:16, Jet Chen <jet.chen@...el.com> wrote:
> Hi Viresh,
>
> I changed your print message as you suggested.
>
> diff --git a/kernel/timer.c b/kernel/timer.c
> index 6c3a371..193101d 100644
> --- a/kernel/timer.c
> +++ b/kernel/timer.c
> @@ -1617,8 +1617,8 @@ static void migrate_timer_list(struct tvec_base
> *new_base, struct list_head *hea
>
>                  /* Check if CPU still has pinned timers */
>                  if (unlikely(WARN(is_pinned,
> -                                 "%s: can't migrate pinned timer: %p,
> deactivating it\n",
> -                                 __func__, timer)))
> +                                 "%s: can't migrate pinned timer: %p,
> timer->function: %p,deactivating it\n",
> +                                 __func__, timer, timer->function)))
>                          continue;
>
> Then I reproduced the issue, and got the dmesg output,
>
> [   37.918406] migrate_timer_list: can't migrate pinned timer:
> ffffffff81f06a60, timer->function: ffffffff810d7010,deactivating it
>
> We reproduced this issue for several times in our LKP system. The address of
> timer ffffffff81f06a60 is very constant. So is timer->function, I believe.
>
> Hope this information will help you. Please feel free to tell me what else I
> can do to help you.

Hi Jet,

Thanks a lot. Yes that's pretty helpful.. But I need some more help from you..
I don't have any idea which function has this address in your kernel:
ffffffff810d7010 :)

Can you please debug that a bit more? You need to find which function
this address belongs to. You can try that using objdump on your vmlinux.

Some help can be found here: Documentation/BUG-HUNTING

Thanks in Advance.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/