Hello,
On 09/03/2010 07:47 AM, Kiyoshi Ueda wrote:
> Ah, I see, thank you for the quick fix!
> I confirmed no panic occurs with this patch.
>
> Tested-by: Kiyoshi Ueda <k-ueda@xxxxxxxxxxxxx>
Great, thanks for testing.
> By the way, I had been considering a block-layer interface which remaps
> struct request and its bios to a block device such as:
> void blk_remap_request(struct request *rq, struct block_device *bdev)
> {
> rq->rq_disk = bdev->bd_disk;
>
> __rq_for_each_bio(bio, rq) {
> bio->bi_bdev = bdev->bd_disk;
> }
> }
>
> If there is such an interface and remapping drivers use it, then these
> kind of issues may be avoided in the future.
I think the problem is more with request initialization. After all,
once bios are packed into a request, they are (or at least should be)
just data containers. We now have multiple request init paths in
block layer and different ones initialize different subsets and it's
not very clear which fields are supposed to be initialized to what by
whom.
But yeah I agree removing discrepancy between request and bio would be
nice to have too. It's not really remapping tho. Maybe just
blk_set_rq_q() or something like that (it should also set rq->q)?
Thanks.
--
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
