lkml.org 
[lkml]   [2013]   [Jan]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    SubjectRe: [next-20130114] Call-trace in LTP (lite) madvise02 test (block|mm|vfs related?)
    From
    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


    \
     
     \ /
      Last update: 2013-01-16 11:01    [W:3.456 / U:0.008 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site