All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Morris <jmorris@namei.org>
To: antoine <antoine@nagafix.co.uk>
Cc: linux-kernel@vger.kernel.org, "Stephen D. Smalley" <sds@epoch.ncsc.mil>
Subject: Re: preempt with selinux NULL pointer dereference
Date: Fri, 5 Aug 2005 10:25:04 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.63.0508051024100.559@excalibur.intercode> (raw)
In-Reply-To: <1123234785.7889.7.camel@dhcp-192-168-22-217.internal>

On Fri, 5 Aug 2005, antoine wrote:

> After using it for a good few hours, I launched a shell script in a terminal and got the traces below.
> I hope this helps (if not, please let me know how to make it helpful or I'll just stop testing -rc kernels and save myself some time)
>
>
> [ 4788.218951] Unable to handle kernel NULL pointer dereference at 0000000000000028 RIP:
> [ 4788.218959] <ffffffff80247381>{inode_has_perm+81}
> [ 4788.218971] PGD 2485f067 PUD 0
> [ 4788.218975] Oops: 0000 [1] PREEMPT
> [ 4788.218977] CPU 0
> [ 4788.218979] Modules linked in: parport_pc lp parport eeprom i2c_sensor i2c_viapro i2c_dev i2c_core rfcomm l2cap bluetooth sunrpc ipt_REJECT ipt_state ip_conntrack iptable_filter ip_tables dm_mod hotkey container tsdev usbhid yenta_socket rsrc_nonstatic uhci_hcd ehci_hcd shpchp via_ircc irda crc_ccitt
> [ 4788.218995] Pid: 19002, comm: ssh Tainted: G   M  2.6.13-rc5

Which of your modules is non-GPL and can you please remove them and see if 
there's still a problem?



- James
-- 
James Morris
<jmorris@namei.org>

  reply	other threads:[~2005-08-05 14:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-05  9:39 preempt with selinux NULL pointer dereference antoine
2005-08-05 14:25 ` James Morris [this message]
2005-08-05 16:46   ` Antoine Martin
2005-08-05 17:10     ` James Morris
2005-08-05 17:19     ` linux-os (Dick Johnson)
2005-08-05 18:50       ` Dave Jones
2005-08-05 19:30         ` linux-os (Dick Johnson)
2005-08-05 18:09     ` Marc Ballarin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.63.0508051024100.559@excalibur.intercode \
    --to=jmorris@namei.org \
    --cc=antoine@nagafix.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sds@epoch.ncsc.mil \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.