Shaohua Li <ShLi@xxxxxxxxxxxx> writes: > On 10/18/13 5:58 AM, "Jes Sorensen" <Jes.Sorensen@xxxxxxxxxx> 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? > > The raid5 trim support is in upstream since v3.7, can you please try an > old kernel to check if this is a regression? For example, 3.11, 3.10? > Looks we have some problems with discard request payload from the oops log. I went as far back and explicitly checked out the git commit that introduced raid5 trim support: git checkout 620125f2bf8ff0c4969b79653b54d7bcc9d40637 Same problem there. 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
