From mboxrd@z Thu Jan 1 00:00:00 1970 From: Shaohua Li Subject: Re: raid5 trim OOPS / use after free? Date: Thu, 17 Oct 2013 23:30:31 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8BIT Return-path: In-Reply-To: Content-Language: en-US Content-ID: Sender: linux-raid-owner@vger.kernel.org To: Jes Sorensen , "linux-raid@vger.kernel.org" Cc: NeilBrown , Jeff Moyer List-Id: linux-raid.ids On 10/18/13 5:58 AM, "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? 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. Thanks, Shaohua