Thread (8 messages) 8 messages, 3 authors, 2013-01-16

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

From: Stephen Rothwell <hidden>
Date: 2013-01-15 03:11:02
Also in: linux-fsdevel, linux-next, lkml

Hi all,

On Mon, 14 Jan 2013 22:09:18 +0100 Sedat Dilek [off-list ref] wrote:
Looks like this is the fix from Sasha [1].
Culprit commit is [2].
Testing...

- Sedat -

[1] https://patchwork.kernel.org/patch/1973481/
OK, I added this patch ("mm: fix BUG on madvise early failure") to the
copy of the akpm tree in linux-next today.
[2] http://git.kernel.org/?p=linux/kernel/git/next/linux-next.git;a=commitdiff;h=0d18d770b9180ffc2c3f63b9eb8406ef80105e05
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

Attachments

Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help