Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751858AbbHTLDS (ORCPT ); Thu, 20 Aug 2015 07:03:18 -0400 Received: from twin.jikos.cz ([89.185.236.188]:54011 "EHLO twin.jikos.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751094AbbHTLDR (ORCPT ); Thu, 20 Aug 2015 07:03:17 -0400 X-Greylist: delayed 560 seconds by postgrey-1.27 at vger.kernel.org; Thu, 20 Aug 2015 07:03:17 EDT Date: Thu, 20 Aug 2015 12:53:54 +0200 (CEST) From: Jiri Kosina X-X-Sender: jikos@twin.jikos.cz To: Muni Sekhar cc: linux-kernel@vger.kernel.org Subject: =?ISO-8859-7?Q?Re=3A_Debugging_General_Protection_Fault=A2s?= In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (LRH 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=UTF-8 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 882 Lines: 25 On Tue, 18 Aug 2015, Muni Sekhar wrote: > [ Please keep me in CC as I'm not subscribed to the list] > > Hello, > > I have a doubt regarding debugging general protection fault’s. > I am running the driver tests on Intel(R) Core(TM)2 Duo CPU. > During the tests I see system hangs after continuous occurrence of > general protection fault’s. > > First fault occurred on CPU: 0 , but it is not related to our driver, There is no evidence that this is not caused by your driver. It's #GP in __kmalloc(), which might very well be caused by use after free in your driver, corrupting slab metadata or so. -- Jiri Kosina SUSE Labs -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/