Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 22 Nov 2001 08:05:52 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 22 Nov 2001 08:05:43 -0500 Received: from ns.caldera.de ([212.34.180.1]:20102 "EHLO ns.caldera.de") by vger.kernel.org with ESMTP id ; Thu, 22 Nov 2001 08:05:33 -0500 Date: Thu, 22 Nov 2001 14:05:17 +0100 From: Christoph Hellwig To: Horst von Brand Cc: Linux Kernel Mailing List Subject: Re: [PATCH] Remove needless BKL from release functions Message-ID: <20011122140517.A20826@caldera.de> Mail-Followup-To: Christoph Hellwig , Horst von Brand , Linux Kernel Mailing List In-Reply-To: <200111221230.fAMCU6QJ007258@pincoya.inf.utfsm.cl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200111221230.fAMCU6QJ007258@pincoya.inf.utfsm.cl>; from vonbrand@inf.utfsm.cl on Thu, Nov 22, 2001 at 09:30:06AM -0300 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Nov 22, 2001 at 09:30:06AM -0300, Horst von Brand wrote: > > Nope, it's fine to remove it. Input is racy all over the place and the list > > are modified somewhere else without any locking anyways. > > "It is broken anyway, breaking it some more makes no difference"!? Wether you lock access to shared data at one or zero points doesn't matter, so it's not breaking it more. Christoph -- Of course it doesn't work. We've performed a software upgrade. - 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/