On Friday 26 September 2008, Alan Cox wrote:
quoted text
> parport: quickfix the proc registration bug
>
> From: Alan Cox <alan@redhat.com>
>
> Ideally we should have a directory of drivers and a link to the
> 'active' driver. For now just show the first device which is
> effectively the existing semantics without a warning.
>
> Signed-off-by: Alan Cox <alan@redhat.com>

Thanks Greg, but I'm afraid that still gives me the error:

ppdev0: registered pardevice
sysctl table check failed: /dev/parport/parport0/devices/ppdev0/timeslice  
Sysctl already exists
Pid: 7104, comm: hpijs Not tainted 2.6.27-rc7 #21

Call Trace:
 [<ffffffff8024d2ac>] set_fail+0x48/0x53
 [<ffffffff8024d7a1>] sysctl_check_table+0x4ea/0x531
 [<ffffffff8024d7ba>] sysctl_check_table+0x503/0x531
 [<ffffffff8024d7ba>] sysctl_check_table+0x503/0x531
 [<ffffffff8024d7ba>] sysctl_check_table+0x503/0x531
 [<ffffffff8024d7ba>] sysctl_check_table+0x503/0x531
 [<ffffffff8024d7ba>] sysctl_check_table+0x503/0x531
 [<ffffffff8023b378>] ? sysctl_set_parent+0x24/0x39
 [<ffffffff8023c66e>] __register_sysctl_paths+0xee/0x29e
 [<ffffffff80314f05>] ? sprintf+0x68/0x6a
 [<ffffffff8023c847>] register_sysctl_paths+0x29/0x2b
 [<ffffffff8023c85c>] register_sysctl_table+0x13/0x15
 [<ffffffffa00f79d4>] parport_device_proc_register+0xcc/0xf0 [parport]
 [<ffffffffa00f5a07>] parport_register_device+0x25c/0x296 [parport]
 [<ffffffffa03c9a3b>] ? pp_irq+0x0/0x4b [ppdev]
 [<ffffffffa03c93e2>] pp_ioctl+0x16f/0x7c8 [ppdev]
 [<ffffffff80282894>] ? free_pages_and_swap_cache+0x57/0x72
 [<ffffffff8029abbe>] vfs_ioctl+0x2a/0x78
 [<ffffffff8029ae63>] do_vfs_ioctl+0x257/0x274
 [<ffffffff8029aed5>] sys_ioctl+0x55/0x78
 [<ffffffff8020c1eb>] system_call_fastpath+0x16/0x1b

ppdev0: registered pardevice
ppdev0: unregistered pardevice
ppdev0: unregistered pardevice

Cheers,
FJP
--
unsubscribe notice
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/