Re: Locking bugs in 2.4 md.c

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

 



On Friday September 19, lmb@suse.de wrote:
> On 2003-09-19T09:26:10,
>    Lars Marowsky-Bree <lmb@suse.de> 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.
> 
> Hi Neil, turns out your patch did exactly what I did with lock_mddev(),
> just with a bigger granularity (which I think is a good thing, but I was
> too shy to introduce a new lock).
> 
> However, I can still reliably panic the kernel with the sequence I gave
> on a SMP box, even though the panic now seems to occur in different
> places...

I can't !!
If you can show me a stack trace or some pointers to wher it panics, I
can look further.

NeilBrown
-
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