From: Christoph Hellwig <hch@lst.de>
To: Pavel Roskin <proski@gnu.org>
Cc: Christoph Hellwig <hch@lst.de>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.5.68-bk1 crash in devfs_remove() for defpts files
Date: Mon, 21 Apr 2003 22:57:04 +0200 [thread overview]
Message-ID: <20030421225704.A30489@lst.de> (raw)
In-Reply-To: <Pine.LNX.4.55.0304211630230.2599@marabou.research.att.com>; from proski@gnu.org on Mon, Apr 21, 2003 at 04:35:21PM -0400
On Mon, Apr 21, 2003 at 04:35:21PM -0400, Pavel Roskin wrote:
> > 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:
>
> Applied. Now I can log in by ssh and there are no problems with
> pseudoterminals. However, all local terminals are gone:
The devfs <-> tty interaction are going to drive me nuts.
TTY_DRIVER_NO_DEVFS actually means don't call tty_register_device
in tty_register_driver, not don't register with devfs.
Updated patch (replaces the last one):
--- 1.78/drivers/char/tty_io.c Sat Apr 19 19:24:04 2003
+++ edited/drivers/char/tty_io.c Mon Apr 21 21:28:01 2003
@@ -2173,9 +2173,9 @@
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);
+ if (!(driver->flags & TTY_DRIVER_NO_DEVFS)) {
+ for (i = 0; i < driver->num; i++)
+ tty_register_device(driver, driver->minor_start + i);
}
proc_tty_register_driver(driver);
return error;
@@ -2215,7 +2215,8 @@
driver->termios_locked[i] = NULL;
kfree(tp);
}
- tty_unregister_device(driver, driver->minor_start + i);
+ if (!(driver->flags & TTY_DRIVER_NO_DEVFS))
+ tty_unregister_device(driver, driver->minor_start + i);
}
proc_tty_unregister_driver(driver);
return 0;
next prev parent reply other threads:[~2003-04-21 20:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-21 17:49 [PATCH] 2.5.68-bk1 crash in devfs_remove() for defpts files Pavel Roskin
2003-04-21 17:55 ` Christoph Hellwig
2003-04-21 17:58 ` Christoph Hellwig
2003-04-21 18:53 ` Pavel Roskin
2003-04-21 19:00 ` Christoph Hellwig
2003-04-21 19:44 ` Pavel Roskin
2003-04-21 19:56 ` Christoph Hellwig
2003-04-21 20:35 ` Pavel Roskin
2003-04-21 20:44 ` Grzegorz Jaskiewicz
2003-04-21 20:56 ` Pavel Roskin
2003-04-24 7:39 ` Martin Schlemmer
2003-04-24 7:57 ` Grzegorz Jaskiewicz
2003-04-24 11:46 ` Martin Schlemmer
2003-04-24 12:03 ` Grzegorz Jaskiewicz
2003-04-21 20:57 ` Christoph Hellwig [this message]
2003-04-21 21:15 ` Pavel Roskin
2003-04-21 21:23 ` Christoph Hellwig
2003-04-21 21:45 ` Pavel Roskin
2003-04-21 22:25 ` Christoph Hellwig
2003-04-21 22:37 ` Pavel Roskin
-- strict thread matches above, loose matches on Subject: below --
2003-04-22 10:12 Chuck Ebbert
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=20030421225704.A30489@lst.de \
--to=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=proski@gnu.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox