Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sun, 25 Feb 2001 19:49:05 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sun, 25 Feb 2001 19:48:56 -0500 Received: from ns.virtualhost.dk ([195.184.98.160]:23822 "EHLO virtualhost.dk") by vger.kernel.org with ESMTP id ; Sun, 25 Feb 2001 19:48:45 -0500 Date: Mon, 26 Feb 2001 01:48:27 +0100 From: Jens Axboe To: Alexander Viro Cc: Nate Eldredge , linux-kernel@vger.kernel.org Subject: Re: 2.4.2-ac3: loop threads in D state Message-ID: <20010226014827.Z7830@suse.de> In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: ; from viro@math.psu.edu on Sun, Feb 25, 2001 at 07:40:42PM -0500 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Feb 25 2001, Alexander Viro wrote: > Let me elaborate: the race is very narrow and takes deliberate efforts to > hit. It _can_ be triggered, unfortunately. This extra up() will mess your > life later on. What's the worst that can happen? We do an extra up, but loop_thread will still quit once we hit zero lo_pending. And loop_clr_fd is still protected by lo_ctl_mutex. -- Jens Axboe - 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/