Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1209287 > unrolled thread

Debugging General Protection Fault’s

Back to article view | Back to linux.kernel

Contents

  Debugging General Protection Fault’s Muni Sekhar <munisekharrms@gmail.com> - 2015-08-18 16:40 +0200
    Re: Debugging General Protection Fault’s Jiri Kosina <jikos@kernel.org> - 2015-08-20 13:10 +0200

#1209287 — Debugging General Protection Fault’s

[Multipart message — attachments visible in raw view] — view raw

 [ 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,
looks like it is in kernel stack.
Second gpf fault and third Oops fault related to our own driver. Rest
other looks to be in kernel stack.

I would like to know, is the first fault triggered other faults?
Is all the faults needs to be fixed or just the first fault?

 Full stack trace is attached.

 [009298.685954] general protection fault: 0000 [#1] SMP
 [009298.725436] general protection fault: 0000 [#2] SMP
 [009298.866588] Oops: 0002 [#3] SMP
 [009300.134033] general protection fault: 0000 [#4] SMP


Regards,
Sekhar

[toc] | [next] | [standalone]

#1210417

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/

[toc] | [prev] | [standalone]

Back to top | Article view | linux.kernel

csiph-web