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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Jan 15, 2013 at 4:11 AM, Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx> wrote:
> Hi all,
>
> On Mon, 14 Jan 2013 22:09:18 +0100 Sedat Dilek <sedat.dilek@xxxxxxxxx> 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@xxxxxxxxx@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@xxxxxxxxxxxxxxxx
--
To unsubscribe from this list: send the line "unsubscribe linux-next" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Kernel]     [Linux USB Development]     [Yosemite News]     [Linux SCSI]

  Powered by Linux