From: Shaohua Li <ShLi@fusionio.com>
To: Jes Sorensen <Jes.Sorensen@redhat.com>,
"linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Cc: NeilBrown <neilb@suse.de>, Jeff Moyer <jmoyer@redhat.com>
Subject: Re: raid5 trim OOPS / use after free?
Date: Thu, 17 Oct 2013 23:30:31 +0000 [thread overview]
Message-ID: <CE8692DA.64C5%shli@fusionio.com> (raw)
In-Reply-To: <wrfj61svftky.fsf@redhat.com>
On 10/18/13 5:58 AM, "Jes Sorensen" <Jes.Sorensen@redhat.com> 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
next prev parent reply other threads:[~2013-10-17 23:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-17 21:58 raid5 trim OOPS / use after free? Jes Sorensen
2013-10-17 23:14 ` Stan Hoeppner
2013-10-18 6:03 ` Jes Sorensen
2013-10-19 6:54 ` Shaohua Li
2013-10-21 12:29 ` Jes Sorensen
2013-10-21 18:23 ` DeGon, Michael J
2013-10-22 8:36 ` Jes Sorensen
2013-10-25 11:37 ` Jes Sorensen
2013-10-17 23:30 ` Shaohua Li [this message]
2013-10-18 6:05 ` Jes Sorensen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CE8692DA.64C5%shli@fusionio.com \
--to=shli@fusionio.com \
--cc=Jes.Sorensen@redhat.com \
--cc=jmoyer@redhat.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).