Re: Locking bugs in 2.4 md.c

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

 



On 2003-09-19T12:08:29,
   Neil Brown <neilb@cse.unsw.edu.au> said:

> A patch against 2.4-current is below.  It probably works but I haven't
> reviewed it in the context of other recent changes to md so I make no
> promises.

Thanks. I'll merge it against the current 2.4.

I had already started putting lock_/unlock_mddev() statements through
potential candidates, but that didn't actually help. raid1d was racy
with md_update_sb somehow, and I couldn't figure out how ;-)

A global lock may indeed be better.

I'll let you know how it goes.


Sincerely,
    Lars Marowsky-Brée <lmb@suse.de>

-- 
High Availability & Clustering		ever tried. ever failed. no matter.
SuSE Labs				try again. fail again. fail better.
Research & Development, SuSE Linux AG		-- Samuel Beckett

-
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