From mboxrd@z Thu Jan 1 00:00:00 1970 From: Linus Torvalds Subject: Re: [PATCH 04/23] vfs: Introduce infrastructure for revoking a file Date: Tue, 2 Jun 2009 10:06:00 -0700 (PDT) Message-ID: References: <1243893048-17031-4-git-send-email-ebiederm@xmission.com> <20090602071411.GE31556@wotan.suse.de> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: "Eric W. Biederman" , Al Viro , linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org, linux-mm@kvack.org, linux-fsdevel@vger.kernel.org, Hugh Dickins , Tejun Heo , Alexey Dobriyan , Alan Cox , Greg Kroah-Hartman , Andrew Morton , Christoph Hellwig , "Eric W. Biederman" To: Nick Piggin Return-path: In-Reply-To: <20090602071411.GE31556@wotan.suse.de> Sender: linux-pci-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Tue, 2 Jun 2009, Nick Piggin wrote: > > Why is it called hotplug? Does it have anything to do with hardware? > Because every concurrently changed software data structure in the > kernel can be "hot"-modified, right? > > Wouldn't file_revoke_lock be more appropriate? I agree, "hotplug" just sounds crazy. It's "open" and "revoke", not "plug" and "unplug". Linus