Oh, I see now. There's a longstanding bug in the handling of
TTY_DRIVER_NO_DEVFS that got exposed by this.
Please try this patch additionally:
--- 1.78/drivers/char/tty_io.c Sat Apr 19 19:24:04 2003
+++ edited/drivers/char/tty_io.c Mon Apr 21 20:33:35 2003
@@ -2139,12 +2139,14 @@
*/
void tty_register_device(struct tty_driver *driver, unsigned minor)
{
- tty_register_devfs(driver, minor);
+ if (!(driver->flags & TTY_DRIVER_NO_DEVFS))
+ tty_register_devfs(driver, minor);
}
void tty_unregister_device(struct tty_driver *driver, unsigned minor)
{
- tty_unregister_devfs(driver, minor);
+ if (!(driver->flags & TTY_DRIVER_NO_DEVFS))
+ tty_unregister_devfs(driver, minor);
}
EXPORT_SYMBOL(tty_register_device);
@@ -2173,10 +2175,8 @@
list_add(&driver->tty_drivers, &tty_drivers);
- if ( !(driver->flags & TTY_DRIVER_NO_DEVFS) ) {
- for(i = 0; i < driver->num; i++)
- tty_register_device(driver, driver->minor_start + i);
- }
+ for (i = 0; i < driver->num; i++)
+ tty_register_device(driver, driver->minor_start + i);
proc_tty_register_driver(driver);
return error;
}
-
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/