From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: [PATCH] fs-private data in struct block_device Date: Fri, 2 Jan 2004 00:23:45 +0100 Sender: linux-fsdevel-owner@vger.kernel.org Message-ID: <20040101232345.GB5143@lst.de> References: <20040101164219.GB654@lst.de> <20040101151017.3f7bc407.akpm@osdl.org> <20040101232137.GR4176@parcelfarce.linux.theplanet.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Andrew Morton , linux-fsdevel@vger.kernel.org Return-path: Received: from verein.lst.de ([212.34.189.10]:48821 "EHLO mail.lst.de") by vger.kernel.org with ESMTP id S261784AbUAAXXu (ORCPT ); Thu, 1 Jan 2004 18:23:50 -0500 To: viro@parcelfarce.linux.theplanet.co.uk Content-Disposition: inline In-Reply-To: <20040101232137.GR4176@parcelfarce.linux.theplanet.co.uk> List-Id: linux-fsdevel.vger.kernel.org On Thu, Jan 01, 2004 at 11:21:37PM +0000, viro@parcelfarce.linux.theplanet.co.uk wrote: > Obvious: we need at least some rules regarding who can and who can not > play with that field. IOW, which filesystem? Okay, let's make it more general. Throw the filesystem completly out of the few and say the private data can be used by the owner of that blockdevice as established by bd_claim, okay?