[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <50F454C2.6000509@kernel.dk>
Date: Mon, 14 Jan 2013 19:56:02 +0100
From: Jens Axboe <axboe@...nel.dk>
To: sedat.dilek@...il.com
CC: linux-next <linux-next@...r.kernel.org>,
linux-fsdevel <linux-fsdevel@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
Stephen Rothwell <sfr@...b.auug.org.au>,
linux-mm <linux-mm@...ck.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Al Viro <viro@...iv.linux.org.uk>
Subject: Re: [next-20130114] Call-trace in LTP (lite) madvise02 test (block|mm|vfs
related?)
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 from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists