mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: ltp-list@lists.sourceforge.net
Cc: naresh kamboju <naresh.kernel@gmail.com>,
	linux-kernel@vger.kernel.org, maxin john <maxinbjohn@gmail.com>,
	brinda_mn@yahoo.co.in, Oleg Nesterov <oleg@redhat.com>,
	tim.bird@am.sony.com, rohit.170309@gmail.com
Subject: Re: [LTP] Char Limit issue on 2.6.29 kernels
Date: Fri, 24 Jul 2009 13:49:56 -0400	[thread overview]
Message-ID: <200907241349.58754.vapier@gentoo.org> (raw)
In-Reply-To: <f5a7b3810907240831t75a058a2m96abdc28a28c4365@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 647 bytes --]

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".  is there a reason you cc-ed LTP ?  is this a crash i a LTP test ?

> 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

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2009-07-24 17:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-24 15:31 naresh kamboju
2009-07-24 17:49 ` Mike Frysinger [this message]
2009-07-24 18:04   ` [LTP] " naresh kamboju
2009-07-24 18:26     ` Tim Bird
2009-07-24 19:16 ` Ray Lee

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200907241349.58754.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=brinda_mn@yahoo.co.in \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ltp-list@lists.sourceforge.net \
    --cc=maxinbjohn@gmail.com \
    --cc=naresh.kernel@gmail.com \
    --cc=oleg@redhat.com \
    --cc=rohit.170309@gmail.com \
    --cc=tim.bird@am.sony.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome