From: "David S. Miller" <davem@davemloft.net>
To: jmacbaine@gmail.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: 2.6.13 crash on sparc64 in sunsu_kbd_ms_interrupt
Date: Mon, 03 Oct 2005 16:56:16 -0700 (PDT) [thread overview]
Message-ID: <20051003.165616.70305022.davem@davemloft.net> (raw)
In-Reply-To: <20051003.165046.126193591.davem@davemloft.net>
From: "David S. Miller" <davem@davemloft.net>
Date: Mon, 03 Oct 2005 16:50:46 -0700 (PDT)
> Please turn off CONFIG_PREEMPT on sparc64, it really doesn't
> get very much testing on this platform.
Nevermind, there is a real bug there in the sunsu driver.
We drop/retake the lock when it's not actually held.
The preempt debugging was good at catching this. :-)
Please try this fix, thanks.
diff-tree 62ba86fc7c72edc77a67e04b6fb593db5046cc92 (from baaf9033270c9cb10c1441195bc1a0a7665bee7e)
Author: David S. Miller <davem@sunset.davemloft.net>
Date: Mon Oct 3 16:55:10 2005 -0700
[SUNSU]: Fix bogus locking in sunsu_change_mouse_baud()
The lock is not held when calling this function, so we
shouldn't drop then reacquire it.
Based upon a report from Jim MacBaine.
Signed-off-by: David S. Miller <davem@davemloft.net>
diff --git a/drivers/serial/sunsu.c b/drivers/serial/sunsu.c
--- a/drivers/serial/sunsu.c
+++ b/drivers/serial/sunsu.c
@@ -518,11 +518,7 @@ static void sunsu_change_mouse_baud(stru
quot = up->port.uartclk / (16 * new_baud);
- spin_unlock(&up->port.lock);
-
sunsu_change_speed(&up->port, up->cflag, 0, quot);
-
- spin_lock(&up->port.lock);
}
static void receive_kbd_ms_chars(struct uart_sunsu_port *up, struct pt_regs *regs, int is_break)
prev parent reply other threads:[~2005-10-03 23:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-31 15:51 PROBLEM: 2.6.13 crash on sparc64 in sunsu_kbd_ms_interrupt Jim MacBaine
2005-10-03 23:50 ` David S. Miller
2005-10-03 23:56 ` David S. Miller [this message]
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=20051003.165616.70305022.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jmacbaine@gmail.com \
--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