Re: general protection fault: 0000 -#1] SMP

[Justin Mattock]

----- Original Message -----
From: Lin Ming <mlin@xxxxxxxxxxxxx>
To: Justin Mattock <justinmattock@xxxxxxxxx>
Cc: "refpolicy@xxxxxxxxxxxxxx" <refpolicy@xxxxxxxxxxxxxx>; "selinux@xxxxxxxxxxxxx" <selinux@xxxxxxxxxxxxx>; "linux-kernel@xxxxxxxxxxxxxxx" <linux-kernel@xxxxxxxxxxxxxxx>
Sent: Thursday, September 15, 2011 8:00 PM
Subject: Re: general protection fault: 0000 -#1] SMP

On Thu, Sep 15, 2011 at 11:05 PM, Justin Mattock
<justinmattock@xxxxxxxxx> wrote:
>
>
> using the current mainline, I woke the machine up from suspend, then started to relabel the filesystem, using the stable release policy(MCS). then this showed up:
> I only have photos of the crash, due to a total system lock
> http://www.flickr.com/photos/44066293@N08/6149812345/in/photostream
> http://www.flickr.com/photos/44066293@N08/6149811913/in/photostream

Is this a regression? Does it happen for 3.0 kernel?

from looking at the archives I dont see this as a regression. last I reported somethig was in 2010
https://lkml.org/lkml/2010/7/3/155
but I could be wrong.


It crashed at __list_del_entry.
Could you enable CONFIG_DEBUG_LIST=y to get more info?

yeah this is set already in my .config. from what I remember this occured two times,
once after S2R wakeup, then on the first initial install of repolicy(tar ball stable) when .autorelabel went into play.
(but could not capture any thing due to the system doing an instant reboot.
I will keep an eye out on this. I have also update the policy to the current git(not sure if it matters or not).

Lin Ming

>
> Note: I subscribed using my yahoo accnt due to changing, but for some reason, am not able to complete the process
> (will try again to see).
>
> if you need more info let me know(I will try and recreate this, and possibly due a bisect on the kernel and/or pull refpolicy git to see)
>
> Justin P. Mattock


Justin P. Mattock

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/