On Fri, 26 Aug 2005, James Bottomley wrote: > On Fri, 2005-08-26 at 14:52 -0700, Andrew Morton wrote: > > Is there not some nasty little hack we can do to make the crash go away in > > the interim? > > Well, it's nasty. The problem is that klist_next() refers to the > previous element to get the next one. However, this previous element > has just been removed and freed. We could try to open code the > necessary gets and puts in next_device(). > > Could someone check the attached, I think it's the correct open coding? Hmm, basic loading and unloading tests appear to be fine with the patch. I'll try to allocate some additional boxes for weekend runs. Seems minimal, hopefully it will make it into 2.6.13. -- av - : send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
