linux-kernel - Re: crash in 3.12.51 (likely in 3.12.52 as well) in timer code

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: <alpine.DEB.2.11.1602040954310.25254@nanos>
Date:	Thu, 4 Feb 2016 09:56:00 +0100 (CET)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Nikolay Borisov <kernel@...p.com>
cc:	"Linux-Kernel@...r. Kernel. Org" <linux-kernel@...r.kernel.org>,
	Jiri Slaby <jslaby@...e.cz>, Oleg Nesterov <oleg@...hat.com>,
	SiteGround Operations <operations@...eground.com>
Subject: Re: crash in 3.12.51 (likely in 3.12.52 as well) in timer code

On Wed, 3 Feb 2016, Nikolay Borisov wrote:
> 
> It seems when the code tries to do prev->next = next in __list_del from detach_timer, 
> rax has a value of dead000000200200 (LIST_POISON2).

> So in this case the prev/next entries do not look like corrupted, whereas
> when manipulating the list inside detach_timer they do. This is really
> odd, any ideas how to further debug this?

Please enable

CONFIG_DEBUG_OBJECTS
CONFIG_DEBUG_OBJECTS_TIMERS
CONFIG_DEBUG_OBJECTS_WORK

That should pinpoint the offending code.

Thanks,

	tglx