public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: liubo <liubo2009@cn.fujitsu.com>
To: Sharyathi Nagesh <sharyath@in.ibm.com>
Cc: "Rishikesh K. Rajak" <risrajak@in.ibm.com>,
	ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH][RFC]Testcases mbind01.c and get_mempolicy01 fails with EINVAL
Date: Tue, 03 Nov 2009 17:35:46 +0800	[thread overview]
Message-ID: <4AEFF972.3080405@cn.fujitsu.com> (raw)
In-Reply-To: <4AEFF53D.1010908@in.ibm.com>


[-- Attachment #1.1: Type: text/plain, Size: 2437 bytes --]

Hi

On 11/03/2009 05:17 PM, Sharyathi Nagesh wrote:
> Hi
>     We observed that LTP test cases are failing when run on some of
> the distros
>
> Problem Statement:
>
>     I observed that test cases mbind01.c and get_mempolicy01.c are
> failing during call to get_mempolicy() with error -EINVAL.
>     In the kernel code the error comes from
> ----------------------------------------------------------------
>
> SYSCALL_DEFINE5(get_mempolicy, int __user *, policy,
>                 unsigned long __user *, nmask, unsigned long, maxnode,
>                 unsigned long, addr, unsigned long, flags)
> {
>         int err;
>         int uninitialized_var(pval);
>         nodemask_t nodes;
>
>         if (nmask != NULL && maxnode < MAX_NUMNODES)
>                 return -EINVAL;
>                                                  <== in the kernel code,
> MAX_NUMNODES comes to 512

  Is it better that "MAX_NUMNODES" get from configure file?

  For different platforms may have different  MAX_NUMNODES.


  Regards--
  Liu Bo

> ----------------------------------------------------------------
> Analysis:
>     
>     When kernel config option 'configure maximum number of SMP
> processors and NUMA node'  is set MAX_NUMNODES will be initialized to
> 512 and any call to get_mempolicy() with maxnode value  less than that
> cause the test to fail.
> ----------------------------------------------------------------
> Fix:
>     increase the default maxnode value in the test case to reflect
> this value. maxnode value comes from numaif.h and this patch increase
> the value to 512 from earlier 128.
>
> Note:
>     I will submit it in the format, once the patch is accepted
>
> Thanks
> Yeehaw
>

> ------------------------------------------------------------------------
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay 
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> ------------------------------------------------------------------------
>
> _______________________________________________
> Ltp-list mailing list
> Ltp-list@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/ltp-list
>   


[-- Attachment #1.2: Type: text/html, Size: 4074 bytes --]

[-- Attachment #2: Type: text/plain, Size: 399 bytes --]

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference

[-- Attachment #3: Type: text/plain, Size: 155 bytes --]

_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

  reply	other threads:[~2009-11-03  9:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-03  9:17 [LTP] [PATCH][RFC]Testcases mbind01.c and get_mempolicy01 fails with EINVAL Sharyathi Nagesh
2009-11-03  9:35 ` liubo [this message]
2009-11-07  1:16   ` Sharyathi Nagesh

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=4AEFF972.3080405@cn.fujitsu.com \
    --to=liubo2009@cn.fujitsu.com \
    --cc=ltp-list@lists.sourceforge.net \
    --cc=risrajak@in.ibm.com \
    --cc=sharyath@in.ibm.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