From: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
To: Russell King <rmk@arm.linux.org.uk>
Cc: randall@uph.com, Balbir Singh <balbir_soni@yahoo.com>,
linux-kernel@vger.kernel.org
Subject: Re: Patch: Fix serial module use count (2.4.16 _and_ 2.5)
Date: Fri, 30 Nov 2001 13:11:15 +0100 (MET) [thread overview]
Message-ID: <Pine.GSO.3.96.1011130130031.15249E-100000@delta.ds2.pg.gda.pl> (raw)
In-Reply-To: <20011130105633.A18992@flint.arm.linux.org.uk>
On Fri, 30 Nov 2001, Russell King wrote:
> Have you audited all the tty drivers in 2.4 to make sure that they clean
> up safely?
No, of course not -- if I had got a response like "this looks mostly OK,
but please check other drivers", then I would have certainly done. I
think drivers/tc/zs.c is OK, too, but this was more than a year ago, so I
can't recall now, sorry.
> I don't believe the serial code will clean up safely as it stands for
> starters if block_til_ready in serial.c fails, leaving an interrupt
> in use. Further attempts to open the serial device will probably fail.
>
> Try this as any user with your patch applied:
>
> $ stty -clocal -F /dev/ttyS0
> $ cat /proc/interrupts
> $ cat /dev/ttyS0
> ^c
> $ cat /proc/interrupts
>
> I think you'll find your serial port interrupt is still claimed, despite
> the module being marked as not in use.
Indeed -- maybe something was changed past 2.4.5, after all. I'll check
how things look like these days. I nowhere use serial.c as a module
anymore, as all systems I maintain are now configured for the serial
console, so I might have missed something.
--
+ Maciej W. Rozycki, Technical University of Gdansk, Poland +
+--------------------------------------------------------------+
+ e-mail: macro@ds2.pg.gda.pl, PGP key available +
next prev parent reply other threads:[~2001-11-30 12:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-29 16:06 Patch: Fix serial module use count (2.4.16 _and_ 2.5) Balbir Singh
2001-11-29 16:17 ` Russell King
2001-11-30 4:25 ` BALBIR SINGH
2001-11-30 9:36 ` Russell King
2001-11-30 22:19 ` Mike Fedyk
2001-11-30 23:06 ` Russell King
2001-12-01 0:20 ` Mike Fedyk
2001-11-29 18:03 ` Jeff Randall
2001-11-29 18:12 ` Russell King
2001-11-29 18:44 ` Jeff Randall
2001-11-29 19:05 ` James Simmons
2001-11-30 10:44 ` Maciej W. Rozycki
2001-11-30 10:56 ` Russell King
2001-11-30 12:11 ` Maciej W. Rozycki [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-11-29 13:10 Russell King
2001-11-29 13:48 ` BALBIR SINGH
2001-11-29 15:37 ` Russell King
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=Pine.GSO.3.96.1011130130031.15249E-100000@delta.ds2.pg.gda.pl \
--to=macro@ds2.pg.gda.pl \
--cc=balbir_soni@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=randall@uph.com \
--cc=rmk@arm.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).