From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965257AbcBDI5P (ORCPT ); Thu, 4 Feb 2016 03:57:15 -0500 Received: from www.linutronix.de ([62.245.132.108]:35499 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S965221AbcBDI5N (ORCPT ); Thu, 4 Feb 2016 03:57:13 -0500 Date: Thu, 4 Feb 2016 09:56:00 +0100 (CET) From: Thomas Gleixner To: Nikolay Borisov cc: "Linux-Kernel@Vger. Kernel. Org" , Jiri Slaby , Oleg Nesterov , SiteGround Operations Subject: Re: crash in 3.12.51 (likely in 3.12.52 as well) in timer code In-Reply-To: <56B1DD62.9030900@kyup.com> Message-ID: References: <56B1DD62.9030900@kyup.com> User-Agent: Alpine 2.11 (DEB 23 2013-08-11) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Linutronix-Spam-Score: -1.0 X-Linutronix-Spam-Level: - X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required, ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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