linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sedat Dilek <sedat.dilek@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
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>
Subject: Re: [next-20130114] Call-trace in LTP (lite) madvise02 test (block|mm|vfs related?)
Date: Wed, 16 Jan 2013 10:10:12 +0100	[thread overview]
Message-ID: <CA+icZUV2ChWTudqBL=UdrQXu2e01LZSn7_-MYZuYbPzX0ekvsg@mail.gmail.com> (raw)
In-Reply-To: <20130115141102.9a7d93cf4ea74c759ff9e9d5@canb.auug.org.au>

On Tue, Jan 15, 2013 at 4:11 AM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> 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.
>

Thanks for applying the patch!

Can you add my Tested-by (see [1]), thanks!
( I compiled 8 (in words eight) Linux-Next kernels to catch all
regressions and setup my desired kernel-config options. )

$ uname -r
3.8.0-rc3-next20130114-8-iniza-generic

$ cat /proc/version
Linux version 3.8.0-rc3-next20130114-8-iniza-generic
(sedat.dilek@gmail.com@fambox) (gcc version 4.6.3 (Ubuntu/Linaro
4.6.3-1ubuntu5) ) #1 SMP Tue Jan 15 10:05:32 CET 2013

And YES, I am running that kernel(s) in my daily working environment.
My -8 kernel run successfully all LTP-lite tests...
...which is a good orientation for a localmodconfig-ed kernel (minimal
setup) but does not mean this release has no other bugs which I did
not hit in my environment.

- Sedat -

[1] http://marc.info/?l=linux-mm&m=135819894617603&w=2

>> [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

--
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>

  reply	other threads:[~2013-01-16  9:10 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
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 [this message]
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='CA+icZUV2ChWTudqBL=UdrQXu2e01LZSn7_-MYZuYbPzX0ekvsg@mail.gmail.com' \
    --to=sedat.dilek@gmail.com \
    --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=sfr@canb.auug.org.au \
    --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;
as well as URLs for NNTP newsgroup(s).