From: "Stuart MacDonald" <stuartm@connecttech.com>
To: "kees" <kees@schoen.nl>, <linux-kernel@vger.kernel.org>
Subject: Re: Q serial.c
Date: Fri, 22 Jun 2001 09:51:18 -0400 [thread overview]
Message-ID: <070001c0fb22$69d68460$294b82ce@connecttech.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0106220846150.11538-100000@schoen3.schoen.nl>
From: "kees" <kees@schoen.nl>
> What may happen on a SMP machine if a serial port has been closed and the
> closing stage is at shutdown() in serial.c in the call to free_IRQ and
> BEFORE the IRQ is really shutdown, a new character arrives which causes an
> IRQ? Is it possible that the OTHER cpu takes this interrupt and causes a
> crash?
I'm looking at serial-5.05/serial.c. You'll notice at the
beginning of shutdown the saveflags(); cli(); calls.
This disables interrupts. The uart will not be able to
generate IRQs even if new characters arrive.
..Stu
next prev parent reply other threads:[~2001-06-22 13:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-22 6:49 Q serial.c kees
2001-06-22 13:51 ` Stuart MacDonald [this message]
2001-06-22 15:23 ` Jonathan Lundell
2001-06-22 15:32 ` Stuart MacDonald
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='070001c0fb22$69d68460$294b82ce@connecttech.com' \
--to=stuartm@connecttech.com \
--cc=kees@schoen.nl \
--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