linux-kernel - Re: 2.6.32.1: BUG and panic: unable to handle kernel NULL pointer dereference at 000000000000001f

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

Date:	Tue, 22 Dec 2009 19:33:54 +0100
From:	Peter Palfrader <weasel@...ian.org>
To:	Andi Kleen <andi@...stfloor.org>
Cc:	linux-kernel@...r.kernel.org, DSA <debian-admin@...ts.debian.org>,
	linux-input@...r.kernel.org
Subject: Re: 2.6.32.1: BUG and panic: unable to handle kernel NULL pointer dereference at 000000000000001f

On Tue, 22 Dec 2009, Andi Kleen wrote:

> > [    5.304749] BUG: unable to handle kernel NULL pointer dereference at 000000000000001f
> > ..
> > [    5.308739] Call Trace:
> > [    5.308739]  [<ffffffff810c3840>] kstrdup+0x40/0x70
> > [    5.308739]  [<ffffffff81150d77>] sysfs_new_dirent+0xf7/0x110
> > [    5.308739]  [<ffffffff8115121d>] create_dir+0x3d/0xc0
> > [    5.308739]  [<ffffffff81090af1>] ? autoremove_wake_function+0x11/0x40
> > [    5.308739]  [<ffffffff811512d4>] sysfs_create_dir+0x34/0x50
> > [    5.308739]  [<ffffffff8138e7ea>] ? kobject_get+0x1a/0x30
> > [    5.308739]  [<ffffffff8138e961>] kobject_add_internal+0xe1/0x1e0
> > [    5.308739]  [<ffffffff8138eb78>] kobject_add_varg+0x38/0x60
> > [    5.308739]  [<ffffffff8138ec15>] kobject_init_and_add+0x75/0x90
> > [    5.308739]  [<ffffffff81150560>] ? sysfs_ilookup_test+0x0/0x20
> > [    5.308739]  [<ffffffff8115082d>] ? sysfs_find_dirent+0x2d/0x40
> > [    5.308739]  [<ffffffff81150ec1>] ? sysfs_addrm_finish+0x21/0x250
> > [    5.308739]  [<ffffffff8138e7ea>] ? kobject_get+0x1a/0x30
> > [    5.308739]  [<ffffffff810e6fe4>] ? kmem_cache_alloc+0x84/0xc0
> > [    5.308739]  [<ffffffff814238d4>] bus_add_driver+0x94/0x260
> > [    5.308739]  [<ffffffff81424ed9>] driver_register+0x79/0x160
> > [    5.308739]  [<ffffffff815a28a3>] __hid_register_driver+0x43/0x80
> > [    5.308739]  [<ffffffff81a3d7ff>] ? gyration_init+0x0/0x1b
> > [    5.308739]  [<ffffffff81a3d818>] gyration_init+0x19/0x1b
> 
> Seems to be caused by the "gyration driver" whatever that is. Do you
> have such a USB device?  

Doubtful.

> It could be some module mismatch, it looks suspicious
> and from a quick look the gyration driver does nothing bad 
> in that init path. Try a make clean and remove/rebuild/reinstall all the modules
> on the target system.
> 
> If that doesn't help perhaps disable CONFIG_HID_GYRATION,
> but from your other oops something more seems to be broken anyways.

This is a static kernel - no module support.  Anyway, I also tried
without CONFIG_USB_HID (which pulls in all the other HID_* things) but
no luck.

-- 
                           |  .''`.  ** Debian GNU/Linux **
      Peter Palfrader      | : :' :      The  universal
 http://www.palfrader.org/ | `. `'      Operating System
                           |   `-    http://www.debian.org/
--
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/