public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Love <rml@tech9.net>
To: James Simmons <jsimmons@infradead.org>
Cc: Gerhard Mack <gmack@innerfire.net>, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.5.71 - random console corruption
Date: 16 Jun 2003 16:40:28 -0700	[thread overview]
Message-ID: <1055806828.7069.176.camel@localhost> (raw)
In-Reply-To: <Pine.LNX.4.44.0306170032070.26878-100000@phoenix.infradead.org>

On Mon, 2003-06-16 at 16:34, James Simmons wrote:

> For userland<->kernel transactions we have the console_semaphore to 
> protect us. It is also used for console_callback. The console_semaphore is
> not used internally to protect global variables :-( To do this properly 
> would take quite a bit of work.  

It looks like all these globals need a lock -- they can race on SMP or
with kernel preemption.

Is it really going to be that hard to wrap a lock around their access,
because I think this is going to bite SMP users.

	Robert Love


  reply	other threads:[~2003-06-16 23:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-15  0:59 Linux 2.5.71 - random console corruption Gerhard Mack
2003-06-16 21:27 ` James Simmons
2003-06-16 21:31   ` Robert Love
2003-06-16 23:34     ` James Simmons
2003-06-16 23:40       ` Robert Love [this message]
2003-06-17 20:50         ` James Simmons
2003-06-18  1:50           ` Gerhard Mack
2003-06-18 11:56             ` Grzegorz Jaskiewicz
2003-06-18 16:38               ` James Simmons
2003-06-18 16:20                 ` Grzegorz Jaskiewicz
2003-06-18 20:28                   ` James Simmons
2003-06-18 20:08                     ` Grzegorz Jaskiewicz
2003-06-18 16:55                 ` Gerhard Mack
2003-06-19 20:43           ` Bill Davidsen

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=1055806828.7069.176.camel@localhost \
    --to=rml@tech9.net \
    --cc=gmack@innerfire.net \
    --cc=jsimmons@infradead.org \
    --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