Re: [PATCH] mm: kmemleak: Change kmemleak default buffer size
From: Sankar P
Date: Thu Jun 24 2010 - 03:31:18 EST
On Tue, Jun 22, 2010 at 10:25 PM, Luis R. Rodriguez
<lrodriguez@xxxxxxxxxxx> wrote:
> On Mon, Jun 21, 2010 at 11:58:29PM -0700, Sankar P wrote:
>> If we try to find the memory leaks in kernel that is
>> compiled with 'make defconfig', the default buffer size
>> seem to be inadequate. Change the buffer size from
>> 400 to 1000, which is sufficient in most cases.
>>
>> Signed-off-by: Sankar P <sankar.curiosity@xxxxxxxxx>
>
> What's your full name? Please read the "Developer's Certificate of Origin 1.1"
> It says:
>
> then you just add a line saying
>
> Signed-off-by: Random J Developer <random@xxxxxxxxxxxxxxxxxxxxx>
>
> using your real name (sorry, no pseudonyms or anonymous contributions.)
>
>
> Also you may want to post on a new thread instead of using this old thread
> unless the maintainer is reading this and wants to pick it up.
>
In our part of the world, we dont have lastnames. We just use the
first letter of our father's name as the last name.
I will send the updated patch as a new mail, I thought it will be
easier to follow if all mails belongs to the same thread.
Thanks
> Luis
>
>> ---
>> arch/sh/configs/sh7785lcr_32bit_defconfig | 2 +-
>> 1 files changed, 1 insertions(+), 1 deletions(-)
>>
>> diff --git a/arch/sh/configs/sh7785lcr_32bit_defconfig b/arch/sh/configs/sh7785lcr_32bit_defconfig
>> index 71f39c7..b02e5ae 100644
>> --- a/arch/sh/configs/sh7785lcr_32bit_defconfig
>> +++ b/arch/sh/configs/sh7785lcr_32bit_defconfig
>> @@ -1710,7 +1710,7 @@ CONFIG_SCHEDSTATS=y
>> # CONFIG_DEBUG_OBJECTS is not set
>> # CONFIG_DEBUG_SLAB is not set
>> CONFIG_DEBUG_KMEMLEAK=y
>> -CONFIG_DEBUG_KMEMLEAK_EARLY_LOG_SIZE=400
>> +CONFIG_DEBUG_KMEMLEAK_EARLY_LOG_SIZE=1000
>> # CONFIG_DEBUG_KMEMLEAK_TEST is not set
>> CONFIG_DEBUG_PREEMPT=y
>> # CONFIG_DEBUG_RT_MUTEXES is not set
>> --
>> 1.6.4.2
>>
>
--
Sankar P
http://psankar.blogspot.com
--
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/