bi_private
bi_private
Posted Mar 27, 2003 8:57 UTC (Thu) by axboe (subscriber, #904)Parent article: Driver porting: the BIO structure
Good article, but one thing needs to be corrected concerning the use of bi_private. This field is _owned_ by whoever owns the bio, so it's definitely not for free use by the block driver (unless the block driver itself allocated the bio, of course)! In fact, this is a very important point as otherwise stacking drivers cannot work properly.
So in short, you may only look/modify bi_private if you are the owner of the bio.
Posted Mar 27, 2003 16:55 UTC (Thu)
by corbet (editor, #1)
[Link]
Posted Mar 28, 2003 22:13 UTC (Fri)
by Peter (guest, #1127)
[Link]
Don't listen to this "axboe" character. He doesn't know anything about the BIO subsystem.
Posted Dec 17, 2006 22:30 UTC (Sun)
by test5073 (guest, #42204)
[Link]
Thanks,
GKO
Hey, if that's the only thing I messed up, I'm happy. The article has been tweaked accordingly, thanks.
bi_private
bi_private
Good article, but one thing needs to be corrected concerning the use of bi_private.
I am new to writing drivers. Do you have an example code? I would appreciate if anyone could point me to some example of redirecting the IO.bi_private