Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 10 Sep 2002 15:33:52 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 10 Sep 2002 15:33:51 -0400 Received: from neon-gw-l3.transmeta.com ([63.209.4.196]:57356 "EHLO neon-gw.transmeta.com") by vger.kernel.org with ESMTP id ; Tue, 10 Sep 2002 15:33:49 -0400 Date: Tue, 10 Sep 2002 12:38:09 -0700 (PDT) From: Linus Torvalds To: Oliver Xymoron cc: "David S. Miller" , , , , , , Subject: Re: [linux-usb-devel] Re: [BK PATCH] USB changes for 2.5.34 In-Reply-To: <20020910193228.GL31597@waste.org> 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: 744 Lines: 21 On Tue, 10 Sep 2002, Oliver Xymoron wrote: > > Which still leaves the question, does it really make sense for > FATAL/BUG to forcibly kill the machine? No. It should only be "locally fatal", and it should clearly just do what BUG() does now - kill the process. But that implies very much that you really cannot use FATAL() in general at all, since it would be illegal to use whenever some caller holds some non-local locks (which is almost always the case for most "peripheral code"). Linus - 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/