Re: [BUG] The kernel thread for md RAID1 could cause a md RAID1 array deadlock

om raid1d. > > So we create a new function 'flush_pending_writes' to give that attention, > and call it in freeze_array to be sure that we aren't waiting on raid1d. > > Thanks to "K.Tanaka" <[EMAIL PROTECTED]> for finding and reporting > this proble

Re: [RFC] A SCSI fault injection framework using SystemTap.

Matthew Wilcox wrote: > On Tue, Jan 15, 2008 at 12:04:09PM +0900, K.Tanaka wrote: >> I would like to introduce a SCSI fault injection framework using SystemTap. >> >> Currently, kernel has Fault-injection framework and Faulty mode for md, >> which can also be used for

[BUG] The kernel thread for md RAID1 could cause a md RAID1 array deadlock

This message describes the details about md-RAID1 issue found by testing the md RAID1 using the SCSI fault injection framework. Abstract: Both the error handler for md RAID1 and write access request to the md RAID1 use raid1d kernel thread. The nr_pending flag could cause a race condition in raid

[RFC] A SCSI fault injection framework using SystemTap.

I would like to introduce a SCSI fault injection framework using SystemTap. Currently, kernel has Fault-injection framework and Faulty mode for md, which can also be used for testing the error handling. But, they could only produce fixed type of errors stochastically. In order to simulate more re