[lkml]   [2004]   [Jan]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Possibly wrong BIO usage in ide_multwrite


You have to walk either the active or scratch BIO to satitsfy the FSM for
completion of a "DATA_BLOCK". Where "DATA_BLOCK" is variable in lenght.
Also you may not update or acknowledge the return of any BIOS regardless
until the status of the "DATA_BLOCK" is known. Status is always checked
after the transfer but you are not permitted to check it then in pio
period (excluding soft-poll completions, unsupported in Linux). Only
after the next interrupt returns can you querry the status of the previous
"DATA_BLOCK" transfer. Then and only then can you leave the FSM to deal
with the needs of BLOCK.

Trust that Bartlomiej gets the point, I spent a long time making sure
somebody did before I burned out.


Andre Hedrick
LAD Storage Consulting Group

On Thu, 1 Jan 2004, Christophe Saout wrote:

> Hi!
> I was just investigating where bio->bi_idx gets modified in the kernel.
> I found these lines in ide-disk.c in ide_multwrite (DMA off, TASKFILE_IO
> off):
> > if (++bio->bi_idx >= bio->bi_vcnt) {
> > bio->bi_idx = 0;
> > bio = bio->bi_next;
> > }
> (rq->bio also gets changed but it's protected by the scratch buffer)
> I think changing the bi_idx here is dangerous because
> end_that_request_first needs this value to be unchanged because it
> tracks the progress of the bio processing and updates bi_idx itself.
> And bio->bi_idx = 0 is probably wrong because the bio can be submitted
> with bio->bi_idx > 0 (if the bio was splitted and there are clones that
> share the bio_vec array, like raid or device-mapper code).
> If it really needs to play with bi_idx itself care should be taken to
> reset bi_idx to the original value, not to zero.
> I wasn't able to trigger a problem though, I don't know why exactly,
> perhaps there are paths in __end_that_request_first that are not
> interested in bi_dx. I still think there is something wrong with it.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-ide" in
> the body of a message to
> More majordomo info at

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:59    [W:0.080 / U:5.072 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site