Messages in this thread | | | Date | Tue, 17 Sep 2002 13:36:29 -0700 | From | Andrew Morton <> | Subject | Re: route inode->block_device in 2.5? |
| |
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). - 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/
| |