[next-20130114] Call-trace in LTP (lite) madvise02 test (block|mm|vfs related?)

[next-20130114] Call-trace in LTP (lite) madvise02 test (block|mm|vfs related?) · Sedat Dilek <hidden> · 2013-01-14
Re: [next-20130114] Call-trace in LTP (lite) madvise02 test (block|mm|vfs related?) · Jens Axboe <axboe@kernel.dk> · 2013-01-14
Re: [next-20130114] Call-trace in LTP (lite) madvise02 test (block|mm|vfs related?) · Sedat Dilek <hidden> · 2013-01-14
Re: [next-20130114] Call-trace in LTP (lite) madvise02 test (block|mm|vfs related?) · Sedat Dilek <hidden> · 2013-01-14
Re: [next-20130114] Call-trace in LTP (lite) madvise02 test (block|mm|vfs related?) · Stephen Rothwell <hidden> · 2013-01-15
Re: [next-20130114] Call-trace in LTP (lite) madvise02 test (block|mm|vfs related?) · Sedat Dilek <hidden> · 2013-01-16
Re: [next-20130114] Call-trace in LTP (lite) madvise02 test (block|mm|vfs related?) · Jens Axboe <axboe@kernel.dk> · 2013-01-15
Re: [next-20130114] Call-trace in LTP (lite) madvise02 test (block|mm|vfs related?) · Sedat Dilek <hidden> · 2013-01-15

From: Sedat Dilek <hidden>
Date: 2013-01-14 18:33:43
Also in: linux-fsdevel, linux-mm

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?

Thanks in advance!

Regards,
- Sedat -

Attachments

runltplite-results_3.8.0-rc3-next20130114-5-iniza-generic.txt [text/plain] 278623 bytes · preview
call-trace_ltplite_madvise02_next-20130114.txt [text/plain] 4093 bytes · preview
config-3.8.0-rc3-next20130114-5-iniza-generic [application/octet-stream] 109230 bytes
dmesg_3.8.0-rc3-next20130114-5-iniza-generic.txt [text/plain] 52871 bytes · preview

`h`	back out one level
`j`	next message in thread
`k`	previous message in thread
`l`	drill in
`Esc`	close help / fold thread tree
`?`	toggle this help