From: bulb@ucw.cz
To: linux-kernel@vger.kernel.org
Subject: 2.4.17 OOPS in tty code.
Date: Mon, 21 Jan 2002 15:10:37 +0100 [thread overview]
Message-ID: <20020121151037.A21622@ucw.cz> (raw)
Hello All,
Tty device code causes oopses when closing /dev/console and devfs is used.
The bug is reproducible on 2.4.17 UML port. The uml arch code however does
not seem involved. The problem is, that the tty flip buffer flushing task
somehow remains in the tq_timer task queue when the tty struct is freed.
When the device is subsequently reopened (or the memory allocated for other
purpose), run_task_queue OOPSes when it comes acros the entry, that has
it's pointers overwriten.
The bug is regularly triggered in shutdown process (init seems to
close and reopen /dev/console).
As it's the user-mode port, I don't have standart OOPS message, but I am
willing to provide any backtraces and logs you request.
------------------------------------------------------------------------
- Jan Hudec <bulb@ucw.cz>
next reply other threads:[~2002-01-21 14:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-21 14:10 bulb [this message]
2002-01-21 22:04 ` 2.4.17 OOPS in tty code Jeff Dike
2002-01-21 22:47 ` Richard Gooch
2002-01-21 23:08 ` Andrew Morton
2002-01-31 0:21 ` Jan Hudec
[not found] <009101c1a2cf$704da030$0801a8c0@Stev.org>
2002-01-24 13:18 ` Jan Hudec
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=20020121151037.A21622@ucw.cz \
--to=bulb@ucw.cz \
--cc=linux-kernel@vger.kernel.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