From: Jens Axboe <axboe@kernel.dk>
To: sedat.dilek@gmail.com
Cc: linux-next <linux-next@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-mm <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: [next-20130114] Call-trace in LTP (lite) madvise02 test (block|mm|vfs related?)
Date: Mon, 14 Jan 2013 19:56:02 +0100 [thread overview]
Message-ID: <50F454C2.6000509@kernel.dk> (raw)
In-Reply-To: <CA+icZUW1+BzWCfGkbBiekKO8b6KiyAiyXWAHFmVUey2dHnSTzw@mail.gmail.com>
On 2013-01-14 19:33, Sedat Dilek wrote:
> Hi,
>
> while running LTP lite on my next-20130114 kernel I hit this
> call-trace (file attached).
>
> Looks to me like problem in the block layer, but not sure.
> Might one of the experts have look at it?
Really? 600kb of data to look through? Can't you just paste the actual
error, I can't even find it...
--
Jens Axboe
--
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>
next prev parent reply other threads:[~2013-01-14 18:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-14 18:33 [next-20130114] Call-trace in LTP (lite) madvise02 test (block|mm|vfs related?) Sedat Dilek
2013-01-14 18:56 ` Jens Axboe [this message]
2013-01-14 19:28 ` Sedat Dilek
2013-01-14 21:09 ` Sedat Dilek
2013-01-15 3:11 ` Stephen Rothwell
2013-01-16 9:10 ` Sedat Dilek
2013-01-15 6:44 ` Jens Axboe
2013-01-15 8:09 ` Sedat Dilek
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=50F454C2.6000509@kernel.dk \
--to=axboe@kernel.dk \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=sedat.dilek@gmail.com \
--cc=sfr@canb.auug.org.au \
--cc=viro@zeniv.linux.org.uk \
/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).