linux-kernel - Re: Debugging General Protection Fault’s

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] [day] [month] [year] [list]

Message-ID: <alpine.LRH.2.00.1508201253030.27942@twin.jikos.cz>
Date:	Thu, 20 Aug 2015 12:53:54 +0200 (CEST)
From:	Jiri Kosina <jikos@...nel.org>
To:	Muni Sekhar <munisekharrms@...il.com>
cc:	linux-kernel@...r.kernel.org
Subject: Re: Debugging General Protection Fault’s

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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/