public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
To: Subrata Modak <subrata@linux.vnet.ibm.com>
Cc: ltp-list@lists.sourceforge.net, maxin john <maxinbjohn@gmail.com>,
	brinda_mn@yahoo.co.in, Manas Kumar Nayak <maknayak@in.ibm.com>,
	Oleg Nesterov <oleg@redhat.com>,
	rohit.170309@gmail.com, naresh kamboju <naresh.kernel@gmail.com>
Subject: Re: [LTP] [FIX PATCH] ltp-add_key
Date: Fri, 19 Jun 2009 14:43:17 +0530	[thread overview]
Message-ID: <20090619091317.GA11782@linux.vnet.ibm.com> (raw)
In-Reply-To: <1245346315.5041.42.camel@subratamodak.linux.ibm.com>

* Subrata Modak <subrata@linux.vnet.ibm.com> [2009-06-18 23:01:55]:

> Great to see you fix these issues and send across the fixes. However, i
> remember Kamalesh working on similar type of fixes.
> 
> Lets hear from Kamalesh, whether he has something additional from this
> series of patches, or, some other fixes in each patch apart from what
> you have already provided.
> 
> Kamalesh,
> 
> Would you like to say something here ?
> 
> Another suggestion. Naresh, next time when you send patches pertaining
> to one particular issue observed in several tests, then no. the patches,
> like [PATCH 00/N] to [PATCH N/N].

It could be nice to add a section in ltp-howto on sending patch sets.

> 
> Regards--
> Subrata
> 
> On Thu, 2009-06-18 at 01:48 +0530, naresh kamboju wrote: 
> > Hi,
> > 
> > I have noticed following failures and fixed.
> > 1. add_key01.c
> > 2. add_key02.c
> > 
> > 
> > Please find the patch below and as attachment.
> > 
> > Best regards
> > Naresh Kamboju
> > 
> > Signed-off-by: Naresh Kamboju < naresh.kernel@gmail.com >
> > diff -Naurb a/testcases/kernel/syscalls/add_key/add_key01.c
> > b/testcases/kernel/syscalls/add_key/add_key01.c
> > --- a/testcases/kernel/syscalls/add_key/add_key01.c	2009-05-21
> > 23:39:37.000000000 +0530
> > +++ b/testcases/kernel/syscalls/add_key/add_key01.c	2009-06-17
> > 23:00:15.000000000 +0530
> > @@ -125,7 +125,7 @@
> >          for (lc = 0; TEST_LOOPING(lc); ++lc) {
> >                  Tst_count = 0;
> >                  for (testno = 0; testno < TST_TOTAL; ++testno) {
> > -                     TEST(result = syscall(286, "keyring", "wjkey",
> > NULL, 0, KEY_SPEC_THREAD_KEYRING));     //call add_key()
> > +                     TEST(result = syscall(__NR_add_key, "keyring",
> > "wjkey", NULL, 0, KEY_SPEC_THREAD_KEYRING));     //call add_key()
> >                       if(TEST_RETURN != -1) {
> >          		tst_resm(TPASS, "add_key call succeeded");
> >                          cleanup();
> > @@ -139,4 +139,3 @@
> >          }	
> >          tst_exit();
> >  }
> > -

Can you remove the result variable from the TEST() and make similar
changes to add_keys, set_tid_address, set_thread_area syscalls and
resubmit the patches.

 testcases/kernel/syscalls/add_key/add_key01.c |    3 +--
 1 files changed, 1 insertions(+), 2 deletions(-)

diff --git a/testcases/kernel/syscalls/add_key/add_key01.c b/testcases/kernel/syscalls/add_key/add_key01.c
index 67a4c2f..56fbe1a 100644
--- a/testcases/kernel/syscalls/add_key/add_key01.c
+++ b/testcases/kernel/syscalls/add_key/add_key01.c
@@ -109,7 +109,6 @@ void setup() {
 }
 
 int main(int ac, char **av) {
-        int result;
         int lc;                 /* loop counter */
         char *msg;              /* message returned from parse_opts */
 	
@@ -125,7 +124,7 @@ int main(int ac, char **av) {
         for (lc = 0; TEST_LOOPING(lc); ++lc) {
                 Tst_count = 0;
                 for (testno = 0; testno < TST_TOTAL; ++testno) {
-                     TEST(result = syscall(286, "keyring", "wjkey", NULL, 0, KEY_SPEC_THREAD_KEYRING));     //call add_key()
+                     TEST(syscall(__NR_add_key, "keyring", "wjkey", NULL, 0, KEY_SPEC_THREAD_KEYRING));     //call add_key()
                      if(TEST_RETURN != -1) {
         		tst_resm(TPASS, "add_key call succeeded");
                         cleanup();
			
			
			Kamalesh

------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables unlimited
royalty-free distribution of the report engine for externally facing 
server and web deployment.
http://p.sf.net/sfu/businessobjects
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

  parent reply	other threads:[~2009-06-19  9:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-17 20:18 [LTP] [FIX PATCH] ltp-add_key naresh kamboju
2009-06-18 17:31 ` Subrata Modak
2009-06-19  5:41   ` naresh kamboju
2009-06-19  9:13   ` Kamalesh Babulal [this message]
2009-06-19 12:57     ` naresh kamboju

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=20090619091317.GA11782@linux.vnet.ibm.com \
    --to=kamalesh@linux.vnet.ibm.com \
    --cc=brinda_mn@yahoo.co.in \
    --cc=ltp-list@lists.sourceforge.net \
    --cc=maknayak@in.ibm.com \
    --cc=maxinbjohn@gmail.com \
    --cc=naresh.kernel@gmail.com \
    --cc=oleg@redhat.com \
    --cc=rohit.170309@gmail.com \
    --cc=subrata@linux.vnet.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