From: Nageswara R Sastry <rnsastry@linux.vnet.ibm.com>
To: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [Patch] readlink03 test case fix
Date: Fri, 09 Sep 2011 11:34:08 +0530 [thread overview]
Message-ID: <4E69AC58.3080300@linux.vnet.ibm.com> (raw)
Hello,
Any comments on this patch. Thanks!!
> In readlink03 testcase,
> When 'Symlink Pathname is empty' the return value was 'ENOENT' but with
> newer kernels the return value is 'EINVAL'. The following patch will fix
> this.
>
> readlink03:
> Before patch:
> ...
> readlink03 9 TFAIL : readlink() failed, Symlink Pathname is empty,
> errno=22, expected errno=2
> ...
>
> After patch:
> ...
> readlink03 9 TPASS : readlink(), Symlink Pathname is empty,
> returned errno 22
> readlink03 10 TPASS : readlink(), Symlink Pathname is empty,
> returned errno 22
> ...
>
> Signed-off-by: Nageswara R Sastry<rnsastry@...>
--
Regards
R.Nageswara Sastry
------------------------------------------------------------------------------
Why Cloud-Based Security and Archiving Make Sense
Osterman Research conducted this study that outlines how and why cloud
computing security and archiving is rapidly being adopted across the IT
space for its ease of implementation, lower cost, and increased
reliability. Learn more. http://www.accelacomm.com/jaw/sfnl/114/51425301/
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next reply other threads:[~2011-09-09 6:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-09 6:04 Nageswara R Sastry [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-09-05 10:17 [LTP] [Patch] readlink03 test case fix Nageswara R Sastry
2011-09-09 11:02 ` Cyril Hrubis
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=4E69AC58.3080300@linux.vnet.ibm.com \
--to=rnsastry@linux.vnet.ibm.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