From: Veerendra C <veeren@linux.vnet.ibm.com>
To: subrata@linux.vnet.ibm.com
Cc: ltp-list <ltp-list@lists.sourceforge.net>
Subject: Re: [LTP] capset01 patch
Date: Fri, 08 Jan 2010 11:05:30 +0530 [thread overview]
Message-ID: <4B46C422.7040303@linux.vnet.ibm.com> (raw)
In-Reply-To: <1262864218.12213.38.camel@subratamodak.linux.ibm.com>
Hi Subrata
Including my signature as requested
Signed-off-by: Veerendra C<vechandr@in.ibm.com>
Thanks
Veerendra C
Subrata Modak wrote:
> Can you please Sign-Off this match with your Signature ?
>
> Regards--
> Subrata
>
> On Thu, 2010-01-07 at 12:49 +0530, Veerendra C wrote:
>
>> Hi
>> Here is a patch/attachment to fix the error number and error message ,
>> when the capset() syscall fails.
>>
>>
>> *After applying patch:*
>> capset01 1 TBROK capget() failed: errno=???(38): Function not
>> implemented
>>
>> *Before applying patch:*
>> capset01 1 TBROK capget() failed: TEST_ERRNO=???(0): Success
>>
>>
>> Note: This is in the custom built linux kernel where the capset/capget
>> syscall is not implemented. In normal linux kernel this testcase would
>> just work fine without any errors.
>> *
>> Normal kernel:*
>> capset01 1 TPASS : capset() returned 0
>>
>>
>> Regards
>> Veerendra C
>>
>> plain text document attachment (capset01.patch)
>> --- testcases/kernel/syscalls/capset.orig/capset01.c 2010-01-06 13:29:07.000000000 +0530
>> +++ testcases/kernel/syscalls/capset/capset01.c 2010-01-06 13:50:12.000000000 +0530
>> @@ -89,6 +89,7 @@ static void cleanup();
>> char *TCID = "capset01"; /* Test program identifier. */
>> int TST_TOTAL = 1; /* Total number of test cases. */
>> extern int Tst_count; /* Test Case counter for tst_* routines */
>> +static int exp_enos[] = { EFAULT, EINVAL, EPERM, 0 };
>>
>> static struct __user_cap_header_struct header; /* cap_user_header_t is a pointer
>> to __user_cap_header_struct */
>> @@ -143,6 +144,9 @@ void setup()
>> /* capture signals */
>> tst_sig(NOFORK, DEF_HANDLER, cleanup);
>>
>> + /* Set up the expected error numbers for -e option */
>> + TEST_EXP_ENOS(exp_enos);
>> +
>> /* Pause if that option was specified */
>> TEST_PAUSE;
>>
>>
>> ------------------------------------------------------------------------------
>> This SF.Net email is sponsored by the Verizon Developer Community
>> Take advantage of Verizon's best-in-class app development support
>> A streamlined, 14 day to market process makes app distribution fast and easy
>> Join now and get one step closer to millions of Verizon customers
>> http://p.sf.net/sfu/verizon-dev2dev
>> _______________________________________________ Ltp-list mailing list Ltp-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ltp-list
>>
>
>
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2010-01-08 5:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-07 7:19 [LTP] capset01 patch Veerendra C
2010-01-07 11:36 ` Subrata Modak
2010-01-08 5:35 ` Veerendra C [this message]
2010-01-13 14:19 ` Subrata Modak
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=4B46C422.7040303@linux.vnet.ibm.com \
--to=veeren@linux.vnet.ibm.com \
--cc=ltp-list@lists.sourceforge.net \
--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