raid1 critical sections not protected in 2.4.x?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Folks,

I have been looking at the raid1.c code.  There is a kernel thread
raid1d that could be scheduled on processor A.  Then on processor B,
other raid code could be scheduled as per each block I/O request.

The particular critical section is the usage of the conf variable, and
specifically conf->mirrors.  raid1d reads conf->mirrors[x] while other
parts of the md code alter it simulatenously.

Is this a bug?  It might explain how people see counts get out of wack
on the media...

Thanks
-steve


-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux