From: Sasha Levin <sasha.levin@oracle.com>
To: "Theodore Ts'o" <tytso@mit.edu>,
adilger.kernel@dilger.ca, linux-ext4@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: ext4: WARNING: CPU: 10 PID: 23340 at fs/block_dev.c
Date: Thu, 09 Apr 2015 11:19:45 -0400 [thread overview]
Message-ID: <55269891.3050709@oracle.com> (raw)
In-Reply-To: <20150409151736.GA31268@thunk.org>
On 04/09/2015 11:17 AM, Theodore Ts'o wrote:
> On Thu, Apr 09, 2015 at 10:14:49AM -0400, Sasha Levin wrote:
>> > Hi all,
>> >
>> > I was running xfstests on the latest -next kernel directed at an ext4 mount,
>> > and saw the following on the generic/019 test:
> Hi Sasha,
>
> This isn't a test I normally run; is it a test you've run in the past?
> If so, do you know when it first started failing for you?
Nope, I just got new servers to play with and decided to try xfstests.
I can try bisection if it doesn't sound familiar, but since it's metal
servers it'll take a while.
Thanks,
Sasha
next prev parent reply other threads:[~2015-04-09 15:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-09 14:14 ext4: WARNING: CPU: 10 PID: 23340 at fs/block_dev.c Sasha Levin
2015-04-09 15:17 ` Theodore Ts'o
2015-04-09 15:19 ` Sasha Levin [this message]
2015-04-09 20:27 ` Theodore Ts'o
2015-04-09 20:49 ` Sasha Levin
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=55269891.3050709@oracle.com \
--to=sasha.levin@oracle.com \
--cc=adilger.kernel@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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).