Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S264939AbTFQUix (ORCPT ); Tue, 17 Jun 2003 16:38:53 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S264953AbTFQUix (ORCPT ); Tue, 17 Jun 2003 16:38:53 -0400 Received: from carisma.slowglass.com ([195.224.96.167]:2579 "EHLO phoenix.infradead.org") by vger.kernel.org with ESMTP id S264943AbTFQUg6 (ORCPT ); Tue, 17 Jun 2003 16:36:58 -0400 Date: Tue, 17 Jun 2003 21:50:51 +0100 (BST) From: James Simmons To: Robert Love cc: Gerhard Mack , Subject: Re: Linux 2.5.71 - random console corruption In-Reply-To: <1055806828.7069.176.camel@localhost> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 918 Lines: 22 > > 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. For things like fg_console and currcon it will be. Those variables are used everyway like mad. That is a whole lot of locks. I doubt this issue will be solved until 2.7.X. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/