From: Caspar Zhang <caspar@casparzhang.com>
To: Wanlong Gao <gaowanlong@cn.fujitsu.com>
Cc: LTP list <ltp-list@lists.sourceforge.net>
Subject: Re: [LTP] [PATCH V3] readlink03: fix return value for the syscall readlink()
Date: Thu, 15 Mar 2012 12:01:57 +0800 [thread overview]
Message-ID: <4F6169B5.9020205@casparzhang.com> (raw)
In-Reply-To: <1331783585-18980-1-git-send-email-gaowanlong@cn.fujitsu.com>
Hi,
On 03/15/2012 11:53 AM, Wanlong Gao wrote:
> Since commit http://git.kernel.org/linus/65cfc672
> which added O_PATH support to the *at() calls, the error return for readlink/readlinkat
> for the empty pathname has switched from ENOENT to EINVAL. And this patch merged to linux v2.6.39,
> So LTP commit https://github.com/linux-test-project/ltp/commit/0cc7514
> fix this with the kernel version v2.6.39 compared.
>
> But recently, commit http://git.kernel.org/linus/1fa1e7f6
> which ensure we return ENOENT for the empty pathname for normal lookups.
>
> Now, the patch whitch switch the return value back again is already queued for
> 3.0 and 3.1 stable release.
>
> So, if the return value is EINVAL for empty pathname, it may be a kernel bug, so we
> needn't to check the kernel version but return the "kernel bug" INFO to LTP the users.
Hmmm, picky advice: wrapper the line <= 73 character in commit message.
>
> Signed-off-by: Wanlong Gao <gaowanlong@cn.fujitsu.com>
> Acked-by: Jan Stancek <jstancek@redhat.com>
> ---
[snip]
> + if ((strncmp(test_desc, "Symlink Pathname is empty", 25) == 0) &&
> + TEST_ERRNO == EINVAL)
> + tst_resm(TWARN, "It may be a Kernel Bug, see the patch:\n"
picky advice #2: I think without this \n we can still get a good-looking
warning message.
> + "http://git.kernel.org/linus/1fa1e7f6\n");
I guess \n in this line should be removed.
How do you think?
Thanks,
Caspar
------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here
http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next parent reply other threads:[~2012-03-15 4:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4F61650D.2060308@casparzhang.com>
[not found] ` <1331783585-18980-1-git-send-email-gaowanlong@cn.fujitsu.com>
2012-03-15 4:01 ` Caspar Zhang [this message]
2012-03-15 4:25 ` [LTP] [PATCH V3] readlink03: fix return value for the syscall readlink() Wanlong Gao
[not found] ` <1331785975-20452-1-git-send-email-gaowanlong@cn.fujitsu.com>
2012-03-15 5:22 ` [LTP] [PATCH V4] " Caspar Zhang
2012-03-15 5:40 ` Wanlong Gao
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=4F6169B5.9020205@casparzhang.com \
--to=caspar@casparzhang.com \
--cc=gaowanlong@cn.fujitsu.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