From: Christoph Hellwig <hch@lst.de>
To: viro@parcelfarce.linux.theplanet.co.uk
Cc: Andrew Morton <akpm@osdl.org>, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] fs-private data in struct block_device
Date: Fri, 2 Jan 2004 00:23:45 +0100 [thread overview]
Message-ID: <20040101232345.GB5143@lst.de> (raw)
In-Reply-To: <20040101232137.GR4176@parcelfarce.linux.theplanet.co.uk>
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?
next prev parent reply other threads:[~2004-01-01 23:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-01 16:42 [PATCH] fs-private data in struct block_device Christoph Hellwig
2004-01-01 23:10 ` Andrew Morton
2004-01-01 23:21 ` viro
2004-01-01 23:23 ` Christoph Hellwig [this message]
2004-01-01 23:28 ` viro
2004-01-01 23:32 ` Christoph Hellwig
2004-01-04 22:04 ` Randy.Dunlap
2004-01-01 23:22 ` Christoph Hellwig
2004-01-02 2:43 ` Jeff Garzik
2004-01-02 8:48 ` Christoph Hellwig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040101232345.GB5143@lst.de \
--to=hch@lst.de \
--cc=akpm@osdl.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox