On Sun, Jun 19 2005, Christoph Hellwig wrote: > Modules should use the higher-level blk_rq_map_kern, which they > currently do anyway. > > > Index: linux-2.6/fs/bio.c > =================================================================== > --- linux-2.6.orig/fs/bio.c 2005-06-18 17:26:42.000000000 +0200 > +++ linux-2.6/fs/bio.c 2005-06-18 17:49:31.000000000 +0200 > @@ -1201,7 +1201,6 @@ > EXPORT_SYMBOL(bio_add_page); > EXPORT_SYMBOL(bio_get_nr_vecs); > EXPORT_SYMBOL(bio_unmap_user); > -EXPORT_SYMBOL(bio_map_kern); > EXPORT_SYMBOL(bio_pair_release); > EXPORT_SYMBOL(bio_split); > EXPORT_SYMBOL(bio_split_pool); Why? It would be perfectly legit for stacking driver to set up their own bio with kernel mapped data. As with bio_map_user(), blk_rq_map_kern isn't the only valid user of bio_map_kern(). -- Jens Axboe - : send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
