linux-kernel - Re: kernel panic when reboot

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]

Date:	Fri, 14 Dec 2012 12:02:53 +0100
From:	Borislav Petkov <bp@...en8.de>
To:	Wanlong Gao <gaowanlong@...fujitsu.com>
Cc:	LKML <linux-kernel@...r.kernel.org>, wim@...ana.be,
	Tomas Winkler <tomas.winkler@...el.com>
Subject: Re: kernel panic when reboot

On Fri, Dec 14, 2012 at 05:29:09PM +0800, Wanlong Gao wrote:
> Hi, 
> 
> I hit the kernel panic when reboot the system today, just system reboot can cause kernel panic.
> 
> $ git describe 
> v3.7-7784-g7313264
> 
> The config file is attached.
> And the crash screen is uploaded here http://www.tiikoni.com/tis/view/?id=e187047

AFAICT, it looks like list corruption in the mutex_lock path when
trying to grab the watchdog->lock, when we're coming down from
mei_watchdog_unregister().

Is it reproducible?

Btw, this is pre -rc1 kernel so I wouldn't take any issues it has too
seriously before Linus hasn't done -rc1 at least. Testing arbitrary
points in the history is known to lead to all kinds of issues which
aren't reproducible later in my experience.

Adding a MEI guy to CC just in case.

HTH.

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--
--
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/