Re: [Bugme-new] [Bug 9216] New: Kernel NULL pointer dereference at :usbhid:hiddev_ioctl+0x2f/0xabc

Andrew Morton <[email protected]>
Newsgroups gmane.linux.usb.devel
Message-ID <[email protected]>
On Wed, 24 Oct 2007 05:03:35 -0700 (PDT) [email protected] wrote:

> http://bugzilla.kernel.org/show_bug.cgi?id=9216
> 
>            Summary: Kernel NULL pointer dereference at
>                     :usbhid:hiddev_ioctl+0x2f/0xabc
>            Product: Other
>            Version: 2.5
>      KernelVersion: 2.6.32.1
>           Platform: All
>         OS/Version: Linux
>               Tree: Mainline
>             Status: NEW
>           Severity: normal
>           Priority: P1
>          Component: Modules
>         AssignedTo: [email protected]
>         ReportedBy: [email protected]
> 
> 
> I'm using vanilla 2.6.32.1 patched with UnionFS 2.1.7
> (http://download.filesystems.org/unionfs/unionfs-2.1/unionfs-2.1.7_for_2.6.23.1.diff.gz)
> No other patches are applied.
> 
> Sometimes after waking up from suspend-to-ram, I get the following message in
> the kernel log:
> 
> Unable to handle kernel NULL pointer dereference at 00000000000000c9 RIP:
>  [<ffffffff880599f3>] :usbhid:hiddev_ioctl+0x2f/0xabc
> PGD 1a2ed067 PUD 1a2ee067 PMD 0
> Oops: 0000 [1]
> CPU 0
> Modules linked in: ipv6 pcspkr iptable_filter ip_tables x_tables i2c_viapro
> i2c_                                                                 core
> via_agp dm_mirror scsi_wait_scan sl811_hcd usbhid ohci_hcd uhci_hcd usb_sto    
>                                                             rage ehci_hcd
> usbcore
> Pid: 6018, comm: apcupsd Tainted: G   M    2.6.23.1 #1
> RIP: 0010:[<ffffffff880599f3>]  [<ffffffff880599f3>]
> :usbhid:hiddev_ioctl+0x2f/0                                                    
>             xabc
> RSP: 0018:ffff8100181f7e28  EFLAGS: 00010296
> RAX: 0000000000000001 RBX: 00000000400c4807 RCX: 00007fffa76f5dc0
> RDX: ffff810017192bc0 RSI: ffff810019981000 RDI: ffff81001afd7d18
> RBP: ffff81001a4e6000 R08: ffff810019a73a00 R09: ffffffff880599c4
> R10: 00000000471e0c96 R11: 0000000000000246 R12: 00007fffa76f5dc0
> R13: 00007fffa76f5dc0 R14: 00000000400c4807 R15: 00007fffa76f60d8
> FS:  00002b56040add20(0000) GS:ffffffff805d6000(0000) knlGS:0000000000000000
> CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: 00000000000000c9 CR3: 000000001a2ec000 CR4: 00000000000006e0
> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
> Process apcupsd (pid: 6018, threadinfo ffff8100181f6000, task ffff81001ec9a000)
> Stack:  ffff8100181f7e98 0000000000000086 ffffffff805a2c00 ffff81001ec9a000
>  ffffffff805983a0 ffff81001cd50e40 ffff8100181f7ed8 0000000000000292
>  0000000000000000 ffff8100181f7ed8 ffff8100181f7ed8 0000000000000292
> Call Trace:
>  [<ffffffff8023feee>] hrtimer_cancel+0x10/0x16
>  [<ffffffff804a61e1>] do_nanosleep+0x64/0x7c
>  [<ffffffff80228fbf>] default_wake_function+0x0/0xe
>  [<ffffffff8024021a>] hrtimer_nanosleep+0x7c/0x13b
>  [<ffffffff8027eeb0>] do_ioctl+0x50/0x61
>  [<ffffffff8027ef1c>] vfs_ioctl+0x5b/0x244
>  [<ffffffff8027f178>] sys_ioctl+0x73/0x8b
>  [<ffffffff8020bd3e>] system_call+0x7e/0x83
> 
> 
> Code: 48 8b 88 c8 00 00 00 48 8b bd c8 19 00 00 b8 fb ff ff ff 44
> RIP  [<ffffffff880599f3>] :usbhid:hiddev_ioctl+0x2f/0xabc
>  RSP <ffff8100181f7e28>
> CR2: 00000000000000c9
> 

I bumped the severity on this to "high".

I assume thisis a regression?  That earlier kernels did not have this bug?

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.