public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
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 10:56:33 +0000	[thread overview]
Message-ID: <20011130105633.A18992@flint.arm.linux.org.uk> (raw)
In-Reply-To: <200111291803.fATI37q08404@sword.damocles.com> <Pine.GSO.3.96.1011130112041.15249C-100000@delta.ds2.pg.gda.pl>
In-Reply-To: <Pine.GSO.3.96.1011130112041.15249C-100000@delta.ds2.pg.gda.pl>; from macro@ds2.pg.gda.pl on Fri, Nov 30, 2001 at 11:44:14AM +0100

On Fri, Nov 30, 2001 at 11:44:14AM +0100, Maciej W. Rozycki wrote:
>  Here is a fix I'm using for 2.4.  It was submitted to Alan once, then a
> discussion was performed with a conclusion like "that may be a temporary
> fix for 2.4, but it needs a complete rework for 2.5".  I'm not sure if the
> patch went in anywhere.

Have you audited all the tty drivers in 2.4 to make sure that they clean
up safely?

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.

--
Russell King (rmk@arm.linux.org.uk)                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html


  reply	other threads:[~2001-11-30 10:57 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 [this message]
2001-11-30 12:11       ` Maciej W. Rozycki
  -- 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=20011130105633.A18992@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=balbir_soni@yahoo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=macro@ds2.pg.gda.pl \
    --cc=randall@uph.com \
    /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