Re: [PATCH] mm: fix BUG on madvise early failure

[Sedat Dilek]

On Tue, Jan 15, 2013 at 12:44 AM, Sedat Dilek <sedat.dilek@xxxxxxxxx> wrote:
> On Mon, Jan 14, 2013 at 10:29 PM, Sedat Dilek <sedat.dilek@xxxxxxxxx> wrote:
>> Hi,
>>
>> this patch is for Linux-Next - more exactly next-20130114.
>> Can you please enhance the subject-line of your patch next time.
>>
>> Your patch fixes the issue I have reported a few hours ago in [1].
>>
>> [ TESTCASE ]
>>
>> "madvise02" from Linux Test Project (LTP) see [2]
>>
>> $ cd /opt/ltp/testcases/bin/
>>
>> $ sudo ./madvise02
>> [ OUTPUT ]
>> madvise02    1  TPASS  :  failed as expected: TEST_ERRNO=EINVAL(22):
>> Invalid argument
>> madvise02    2  TPASS  :  failed as expected: TEST_ERRNO=EINVAL(22):
>> Invalid argument
>> madvise02    3  TPASS  :  failed as expected: TEST_ERRNO=EINVAL(22):
>> Invalid argument
>> madvise02    4  TPASS  :  failed as expected: TEST_ERRNO=ENOMEM(12):
>> Cannot allocate memory
>> madvise02    5  TFAIL  :  madvise succeeded unexpectedly
>>
>> [ /TESTCASE ]
>>
>> Please feel free and add a...
>>
>>      Tested-by: Sedat Dilek <sedat.dilek@xxxxxxxxx>
>>
>> Thanks!
>>
>> Regards,
>> - Sedat -
>>
>> [1] http://marc.info/?l=linux-mm&m=135818843710244&w=2
>> [2] http://sourceforge.net/projects/ltp/
>
> You happen to know how I get more verbose-debug outputs?
>
> You have...
>
> [   57.320031] kernel BUG at block/blk-core.c:2981!
> [   57.320031] invalid opcode: 0000 [#3] PREEMPT SMP DEBUG_PAGEALLOC
>
> Me has...
>
> [ 1263.965989] Kernel BUG at ffffffff81328b2b [verbose debug info unavailable]
> [ 1263.966022] invalid opcode: 0000 [#1] SMP
>
> CONFIG_DEBUG_PAGEALLOC=y ?
>
> Block-specific debug settings?
>
> $ egrep -i 'block|blk' .config | egrep -i 'debug|dbg'
> # CONFIG_DEBUG_BLK_CGROUP is not set
> # CONFIG_DEBUG_BLOCK_EXT_DEVT is not set
>

Hmm, DEBUG_PAGEALLOC=y did not help.

Maybe this one...

$ grep DEBUG_BUGVERBOSE .config
# CONFIG_DEBUG_BUGVERBOSE is not set

- Sedat -

> - Sedat -
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/