From: Stephen Rothwell <sfr@canb.auug.org.au>
To: sedat.dilek@gmail.com
Cc: Jens Axboe <axboe@kernel.dk>,
linux-next <linux-next@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
Al Viro <viro@zeniv.linux.org.uk>,
Sasha Levin <sasha.levin@oracle.com>,
Roland McGrath <roland@hack.frob.com>,
Hugh Dickins <hughd@google.com>,
Andy Lutomirski <luto@amacapital.net>,
Shaohua Li <shli@fusionio.com>,
Rik van Riel <riel@redhat.com>linux-mm@kvack.org
Subject: Re: [next-20130114] Call-trace in LTP (lite) madvise02 test (block|mm|vfs related?)
Date: Tue, 15 Jan 2013 14:11:02 +1100 [thread overview]
Message-ID: <20130115141102.9a7d93cf4ea74c759ff9e9d5@canb.auug.org.au> (raw)
In-Reply-To: <CA+icZUV_dz2Bvu6o=YRFu6324ccVr1MaOEpRcw0rguppR5rQQg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 570 bytes --]
Hi all,
On Mon, 14 Jan 2013 22:09:18 +0100 Sedat Dilek <sedat.dilek@gmail.com> 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
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-01-15 20:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-14 18:33 Sedat Dilek
2013-01-14 18:56 ` Jens Axboe
2013-01-14 19:28 ` Sedat Dilek
2013-01-14 21:09 ` Sedat Dilek
2013-01-15 3:11 ` Stephen Rothwell [this message]
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=20130115141102.9a7d93cf4ea74c759ff9e9d5@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=hughd@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=riel@redhat.com \
--cc=roland@hack.frob.com \
--cc=sasha.levin@oracle.com \
--cc=sedat.dilek@gmail.com \
--cc=shli@fusionio.com \
--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