From: Andrew Morton <akpm@digeo.com>
To: Alexander Viro <viro@math.psu.edu>
Cc: Anton Altaparmakov <aia21@cantab.net>,
ptb@it.uc3m.es, linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: route inode->block_device in 2.5?
Date: Tue, 17 Sep 2002 13:36:29 -0700 [thread overview]
Message-ID: <3D87924D.364C4884@digeo.com> (raw)
In-Reply-To: Pine.GSO.4.21.0209170845020.1645-100000@weyl.math.psu.edu
Alexander Viro wrote:
>
> ...
> There might be such thing as underlying block device of a <foofs> inode.
What he said. Generally when the generic layers want to know
what the backing block_device is they defer this all the way down
to the point where they have called the filesystem's ->get_block
callback, and they pluck the block_dev pointer out of bh_result->b_bdev.
That's the only point at which it can be sanely resolved.
It may be different for different blocks of the file (striping;
swap_get_block() did this for the short period when it nearly
existed).
prev parent reply other threads:[~2002-09-17 20:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-12 16:22 route inode->block_device in 2.5? Peter T. Breuer
2002-09-17 12:31 ` Anton Altaparmakov
2002-09-17 13:11 ` Alexander Viro
2002-09-17 20:36 ` Andrew Morton [this message]
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=3D87924D.364C4884@digeo.com \
--to=akpm@digeo.com \
--cc=aia21@cantab.net \
--cc=linux-kernel@vger.kernel.org \
--cc=ptb@it.uc3m.es \
--cc=viro@math.psu.edu \
/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