From: Subrata Modak <subrata@linux.vnet.ibm.com>
To: Henry Yei <hyei@mvista.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH] exit_group01, fix syscall number for exit_group
Date: Thu, 30 Jul 2009 18:14:38 +0530 [thread overview]
Message-ID: <1248957878.5788.19.camel@subratamodak.linux.ibm.com> (raw)
In-Reply-To: <8368651DACC1964480F951191B94A078E49BDE@svexch01.mvista.com>
On Wed, 2009-07-22 at 20:14 -0700, Henry Yei wrote:
> Wei,
>
> If you have time, please make the syscall additions for exit_group.
> I am contributing to LTP out-of-band, so may not get to in a timely manner.
Fine, i will check in Wei Yongjunś patch. Whenever you fell free, please
submit the patch to add an entry as well.
Regards--
Subrata
>
> Thank you!
>
> -----Original Message-----
> From: Wei Yongjun [mailto:yjwei@cn.fujitsu.com]
> Sent: Monday, July 20, 2009 6:07 PM
> To: Henry Yei
> Cc: ltp-list@lists.sourceforge.net
> Subject: Re: [LTP] [PATCH] exit_group01, fix syscall number for exit_group
>
> Hi, Henry Yei
>
> Henry Yei wrote:
> > This issue was found when running on an arm machine.
> >
> >
> > Fix syscall number for exit_group
> >
>
> I have posted the same some days ago, see http://marc.info/?l=ltp-list&m=124798179211554&w=2.
>
> But Garrett Cooper said we also add the relevant syscall number to the architecture specific .in file in testcases/kernel/include. If you have time, you can do this. If you would like to do this, please tell me. So we will not do dup wroks. Thanks.
>
> Wei Yongjun
>
> > <Signed-off-by: Henry Yei <hyei@mvista.com>
> >
> > ---
> > ltp-full-20090531/testcases/kernel/syscalls/exit_group/exit_group01.c
> > 2009-05-21 11:14:40.000000000 -0700
> > +++
> > ltp-full-20090531/testcases/kernel/syscalls/exit_group/exit_group01.c
> > 2009-07-17 12:03:47.000000000 -0700
> > @@ -136,7 +136,7 @@
> > } else if (TEST_RETURN == 0){
> > tst_resm(TINFO, "In the child process");
> > sleep(5);
> > - TEST(syscall(252,4));
> > + TEST(syscall(__NR_exit_group,4));
> > }else {
> > tst_resm(TINFO,"in the parent process");
> > TEST(w = wait(&status));
> >
> >
> > ----------------------------------------------------------------------
> > --
> >
> > ----------------------------------------------------------------------
> > -------- Enter the BlackBerry Developer Challenge This is your chance
> > to win up to $100,000 in prizes! For a limited time, vendors
> > submitting new applications to BlackBerry App World(TM) will have the
> > opportunity to enter the BlackBerry Developer Challenge. See full
> > prize details at: http://p.sf.net/sfu/Challenge
> > ----------------------------------------------------------------------
> > --
> >
> > _______________________________________________
> > Ltp-list mailing list
> > Ltp-list@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/ltp-list
> >
>
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Ltp-list mailing list
> Ltp-list@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/ltp-list
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
prev parent reply other threads:[~2009-07-30 12:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-20 22:06 [LTP] [PATCH] exit_group01, fix syscall number for exit_group Henry Yei
2009-07-21 1:06 ` Wei Yongjun
2009-07-23 3:14 ` Henry Yei
2009-07-30 12:44 ` Subrata Modak [this message]
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=1248957878.5788.19.camel@subratamodak.linux.ibm.com \
--to=subrata@linux.vnet.ibm.com \
--cc=hyei@mvista.com \
--cc=ltp-list@lists.sourceforge.net \
/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