[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f5a7b3810907241104g498b00a6i60c8858b8805091a@mail.gmail.com>
Date: Fri, 24 Jul 2009 23:34:40 +0530
From: naresh kamboju <naresh.kernel@...il.com>
To: Mike Frysinger <vapier@...too.org>
Cc: ltp-list@...ts.sourceforge.net, linux-kernel@...r.kernel.org,
maxin john <maxinbjohn@...il.com>, brinda_mn@...oo.co.in,
Oleg Nesterov <oleg@...hat.com>, tim.bird@...sony.com,
rohit.170309@...il.com
Subject: Re: [LTP] Char Limit issue on 2.6.29 kernels
Hi Mike,
On Fri, Jul 24, 2009 at 11:19 PM, Mike Frysinger<vapier@...too.org> wrote:
> On Friday 24 July 2009 11:31:59 naresh kamboju wrote:
>> I have come across with char Limit issue on 2.6.29 kernels.
>>
>>
>> SIGFAULT:
>>
>> #define SIZE 8053759
>> char buf1[SIZE] ;
>>
>> NO SIGFAULT:
>>
>> #define SIZE 8053758
>> char buf1[SIZE] ;
>>
>> This SIGFAULT not observed on 2.6.23 kernels.
>
> -ENOINFO
>
> post some actual code rather than saying "i declared a large buffer and things
> crashed".
currently i am debugging this issue.
i'll come up with more details.
>is there a reason you cc-ed LTP ? is this a crash i >a LTP test ?
No.
it is not a test cases of LTP.
i am a member of LTP. want to share this information to LTP community.
-naresh
>
>> What could be the changes that effecting from 2.6.23 to 2.6.29 kernels.
>> Please share me the information.
>
> git log v2.6.23..v2.6.29
> -mike
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists