All of lore.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Paul Fulghum <paulkf@microgate.com>
Cc: William Lee Irwin III <wli@holomorphy.com>,
	James Morris <jmorris@redhat.com>, Andrew Morton <akpm@osdl.org>,
	Linux Kernel list <linux-kernel@vger.kernel.org>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: 2.6.9-rc2-mm3
Date: Sat, 25 Sep 2004 10:19:37 +0100	[thread overview]
Message-ID: <20040925101937.A29796@flint.arm.linux.org.uk> (raw)
In-Reply-To: <1096082711.7111.38.camel@at2.pipehead.org>; from paulkf@microgate.com on Fri, Sep 24, 2004 at 10:25:11PM -0500

On Fri, Sep 24, 2004 at 10:25:11PM -0500, Paul Fulghum wrote:
> My suggestion was flawed in that it could
> violate POSIX requirements (as Russell pointed out).
> 
> Removing the lock from tty_termios_baud_rate(), tty_io.c
> corrects the problem for the path from change_termios()
> to tty_termios_baud_rate(), which is causing the deadlock.
> 
> This may not be, and probably is not,
> correct for all paths to tty_termios_baud_rate().

I wonder if we should consider adding:

	WARN_ON(!spin_is_locked(&tty_termios_lock));

in there.

However, the one annoying thing about "spin_is_locked" is that, on UP,
it defaults to "unlocked" which makes these kinds of checks too noisy.
Maybe we need a spin_is_locked() with a bias towards being locked for UP?

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 PCMCIA      - http://pcmcia.arm.linux.org.uk/
                 2.6 Serial core

  reply	other threads:[~2004-09-25  9:19 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-24  8:46 2.6.9-rc2-mm3 Andrew Morton
2004-09-24  9:30 ` 2.6.9-rc2-mm3 William Lee Irwin III
2004-09-24  9:42 ` 2.6.9-rc2-mm3 William Lee Irwin III
2004-09-24 10:11   ` 2.6.9-rc2-mm3 William Lee Irwin III
2004-09-24  9:54 ` 2.6.9-rc2-mm3 Nick Piggin
2004-09-24 10:05   ` 2.6.9-rc2-mm3 Michal Rokos
2004-09-24 10:15     ` 2.6.9-rc2-mm3 Nick Piggin
2004-09-24 10:25   ` 2.6.9-rc2-mm3 William Lee Irwin III
2004-09-24 10:36     ` 2.6.9-rc2-mm3 Nick Piggin
2004-09-24 14:59     ` 2.6.9-rc2-mm3 Michal Rokos
2004-09-24 10:49   ` 2.6.9-rc2-mm3 Arjan van de Ven
2004-09-24 15:29 ` 2.6.9-rc2-mm3 James Morris
2004-09-24 16:16   ` 2.6.9-rc2-mm3 James Morris
2004-09-24 18:45     ` 2.6.9-rc2-mm3 (tty deadlock?) James Morris
2004-09-24 18:52     ` 2.6.9-rc2-mm3 Paul Fulghum
2004-09-24 19:15       ` 2.6.9-rc2-mm3 Paul Fulghum
2004-09-24 19:43         ` 2.6.9-rc2-mm3 Russell King
2004-09-24 20:40           ` 2.6.9-rc2-mm3 Paul Fulghum
2004-09-24 21:11           ` 2.6.9-rc2-mm3 Alan Cox
2004-09-25  1:31     ` 2.6.9-rc2-mm3 William Lee Irwin III
2004-09-25  2:12       ` 2.6.9-rc2-mm3 William Lee Irwin III
2004-09-25  3:25       ` 2.6.9-rc2-mm3 Paul Fulghum
2004-09-25  9:19         ` Russell King [this message]
2004-09-25  9:27           ` 2.6.9-rc2-mm3 Xavier Bestel
2004-09-25 13:20             ` 2.6.9-rc2-mm3 Russell King
2004-09-24 17:01 ` 2.6.9-rc2-mm3 - [PATCH] tmpfs xattr fix James Morris
2004-09-24 18:08 ` 2.6.9-rc2-mm3 (compile stats) John Cherry
2004-09-24 22:35 ` 2.6.9-rc2-mm3, e100 oops J.A. Magallon
2004-09-24 22:38 ` 2.6.9-rc2-mm3, irq 11: nobody cared!, Disabling IRQ #11 J.A. Magallon
2004-09-25 12:43 ` 2.6.9-rc2-mm3 William Lee Irwin III
2004-09-25 16:37   ` 2.6.9-rc2-mm3 Jens Axboe
2004-09-25 17:11     ` 2.6.9-rc2-mm3 William Lee Irwin III
2004-09-25 17:22 ` 2.6.9-rc2-mm3 breaks amanda (was: 2.6.9-rc2-mm3) Matthias Andree
2004-09-25 18:37   ` Gene Heskett
2004-09-25 21:30     ` Matthias Andree
2004-09-26  2:05       ` Gene Heskett
2004-09-25 22:01 ` 2.6.9-rc2-mm3 Alexander Nyberg
2004-09-27 16:02 ` 2.6.9-rc2-mm4 (compile stats) John Cherry

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=20040925101937.A29796@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=akpm@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jmorris@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulkf@microgate.com \
    --cc=wli@holomorphy.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.