Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261956AbTFQG4V (ORCPT ); Tue, 17 Jun 2003 02:56:21 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263791AbTFQG4V (ORCPT ); Tue, 17 Jun 2003 02:56:21 -0400 Received: from ns.suse.de ([213.95.15.193]:43528 "EHLO Cantor.suse.de") by vger.kernel.org with ESMTP id S261956AbTFQG4U (ORCPT ); Tue, 17 Jun 2003 02:56:20 -0400 Date: Tue, 17 Jun 2003 09:09:57 +0200 From: Andi Kleen To: Andrew Morton Cc: "David S. Miller" , ak@suse.de, janiceg@us.ibm.com, linux-kernel@vger.kernel.org, netdev@oss.sgi.com, stekloff@us.ibm.com, girouard@us.ibm.com, lkessler@us.ibm.com, kenistonj@us.ibm.com, jgarzik@pobox.com Subject: Re: patch for common networking error messages Message-ID: <20030617070957.GB2752@wotan.suse.de> References: <3EEE28DE.6040808@us.ibm.com> <20030616.133841.35533284.davem@redhat.com> <20030616205342.GH30400@wotan.suse.de> <20030616.135124.71580008.davem@redhat.com> <20030616152707.58da808c.akpm@digeo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030616152707.58da808c.akpm@digeo.com> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 589 Lines: 15 > Actually it already does, to cover the case where an interrupt handler calls > printk while process-context code is performing a printk. I don't think it'll work. Both printk and release_console_sem take the logbuf_lock, which will deadlock if the same CPU already holds it. It would need to use the usual linux recursive lock hack. -Andi - 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/