From: CAI Qian <caiqian@redhat.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org, linux-mm <linux-mm@kvack.org>,
Steve Best <sbest@redhat.com>
Subject: Re: WARNING: at fs/ext4/inode.c:3222
Date: Thu, 25 Apr 2013 03:26:42 -0400 (EDT) [thread overview]
Message-ID: <1038035954.2119025.1366874802996.JavaMail.root@redhat.com> (raw)
In-Reply-To: <20130425042405.GB4685@thunk.org>
----- Original Message -----
> From: "Theodore Ts'o" <tytso@mit.edu>
> To: "CAI Qian" <caiqian@redhat.com>
> Cc: linux-ext4@vger.kernel.org, "linux-mm" <linux-mm@kvack.org>, "Steve Best" <sbest@redhat.com>
> Sent: Thursday, April 25, 2013 12:24:05 PM
> Subject: Re: WARNING: at fs/ext4/inode.c:3222
>
> On Wed, Apr 24, 2013 at 11:43:20PM -0400, CAI Qian wrote:
> > OK, this is to test the latest ext4 dev tree on power 7 systems
> > running xfstests,
>
> Thanks for reporting this. Was this warning thrown while xfstests 224
> was running? (I like to make sure the xfstests output is sent to the
> console so the kernel messages are intermixed with the xfstests
> output, so it's clear which test triggered the warning.)
Yet to reproduce as only saw it once, but I'll try to see if this is
reproducible.
>
> If so, can you reproduce the problem running xfstest #224 all by
> itself?
>
> Thanks,
>
> - Ted
>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2013-04-25 7:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <84952911.2068510.1366860446300.JavaMail.root@redhat.com>
2013-04-25 3:43 ` WARNING: at fs/ext4/inode.c:3222 CAI Qian
2013-04-25 4:24 ` Theodore Ts'o
2013-04-25 7:26 ` CAI Qian [this message]
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=1038035954.2119025.1366874802996.JavaMail.root@redhat.com \
--to=caiqian@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=sbest@redhat.com \
--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).