Shaohua Li <ShLi@xxxxxxxxxxxx> writes: > On 10/18/13 2:03 PM, "Jes Sorensen" <Jes.Sorensen@xxxxxxxxxx> wrote: > >>Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx> writes: >>> On 10/17/2013 4:58 PM, Jes Sorensen wrote: >>>> Hi, >>>> >>>> I have been trying out the trim code in recent kernels and I am >>>> consistently seeing crashes with the raid5 trim implementation. >>>> >>>> I am seeing 3-4 different OOPS outputs which are very different in >>>>their >>>> output. This makes me suspect this is a memory corruption of use after >>>> free problem? >>>> >>>> Basically I have a system with an AHCI controller and 4 SATA SSD drives >>>> hooked up to it. I create a raid5 and then run mkfs.ext4 on it and the >>>> fireworks display starts. >>>> >>>> I first saw this with an older kernel with some backports applied, but >>>>I >>>> am able to reproduce this with the current top of tree out of Linus' >>>> tree. >>>> >>>> Any ideas? >>> >>> See a nearly identical problem posted to this list yesterday: >>> >>> http://www.spinics.net/lists/raid/msg44686.html >> >>Looks the same - I believe I have seen that variation of the problem as >>well. > > Ok, looks we have some problems with request merge in SCSI. I just posted > some patches to linux-raid maillist, please test and report back. Hi Shaohua, Thanks for the quick reply. I will test them as soon as I can, but it probably wont be until the end of the week. Regards, Jes -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
