From: Xiao Yang <yangx.jy@cn.fujitsu.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] syscalls/copy_file_range02.c: Compatible with new and old kernels
Date: Fri, 31 May 2019 18:15:17 +0800 [thread overview]
Message-ID: <5CF0FEB5.4030700@cn.fujitsu.com> (raw)
In-Reply-To: <1559292243-2882-1-git-send-email-huangjh.jy@cn.fujitsu.com>
On 2019/05/31 16:44, Jinhui huang wrote:
> On new kernels, copy_file_range() returned EISDIR when copyed contents
> to directory, but on old kernels, it returned EBADF, we should accept
> EBADF to be compatible with new and old kernels.
>
> The patch as follows:
> commit 11cbfb10775a ("vfs: deny copy_file_range() for non regular files")
Hi,
From description of commit, I wonder if we can add more tests for some
non regular files(e.g. block, pipe)?
I just want to increase coverage and fix all similar issues as you did. :-)
Best Regards,
Xiao Yang
> Signed-off-by: Jinhui huang <huangjh.jy@cn.fujitsu.com>
> ---
> .../syscalls/copy_file_range/copy_file_range02.c | 33 +++++++++++++++-------
> 1 file changed, 23 insertions(+), 10 deletions(-)
>
> diff --git a/testcases/kernel/syscalls/copy_file_range/copy_file_range02.c b/testcases/kernel/syscalls/copy_file_range/copy_file_range02.c
> index 07c0207..9e6356c 100644
> --- a/testcases/kernel/syscalls/copy_file_range/copy_file_range02.c
> +++ b/testcases/kernel/syscalls/copy_file_range/copy_file_range02.c
> @@ -54,19 +54,32 @@ static void verify_copy_file_range(unsigned int n)
> TEST(sys_copy_file_range(fd_src, 0, *tc->copy_to_fd,
> 0, CONTSIZE, tc->flags));
>
> - if (TST_RET == -1) {
> - if (tc->exp_err == TST_ERR) {
> + if (TST_RET != -1) {
> + tst_res(TFAIL,
> + "copy_file_range returned wrong value: %ld", TST_RET);
> + return;
> + }
> +
> + if (tc->exp_err == TST_ERR) {
> + tst_res(TPASS | TTERRNO,
> + "copy_file_range failed as expected");
> + } else {
> + /* copy_file_range() returned EISDIR when copyed contents to
> + * directory on new kernels, but on old kernels, it returned
> + * EBADF.
> + *
> + * the patch as follws:
> + * commit 11cbfb10775a ("vfs: deny copy_file_range() for non regular files")
> + */
> + if (tc->exp_err == EISDIR && TST_ERR == EBADF) {
> tst_res(TPASS | TTERRNO,
> - "copy_file_range failed as expected");
> - } else {
> - tst_res(TFAIL | TTERRNO,
> - "copy_file_range failed unexpectedly; expected %s, but got",
> - tst_strerrno(tc->exp_err));
> + "copy_file_range failed as expected");
> return;
> }
> - } else {
> - tst_res(TFAIL,
> - "copy_file_range returned wrong value: %ld", TST_RET);
> +
> + tst_res(TFAIL | TTERRNO,
> + "copy_file_range failed unexpectedly; expected %s, but got",
> + tst_strerrno(tc->exp_err));
> }
> }
>
next prev parent reply other threads:[~2019-05-31 10:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-31 8:44 [LTP] [PATCH] syscalls/copy_file_range02.c: Compatible with new and old kernels Jinhui huang
2019-05-31 10:02 ` Li Wang
2019-05-31 10:15 ` Xiao Yang [this message]
2019-05-31 12:03 ` Li Wang
2019-05-31 12:26 ` Cyril Hrubis
2019-05-31 12:46 ` Li Wang
2019-05-31 13:02 ` Amir Goldstein
2019-06-27 8:03 ` Yang Xu
2019-06-27 8:39 ` Amir Goldstein
2019-07-04 10:35 ` Yang Xu
2019-07-04 11:15 ` Amir Goldstein
2019-05-31 11:01 ` Cyril Hrubis
2019-05-31 11:47 ` Li Wang
2019-05-31 12:00 ` 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=5CF0FEB5.4030700@cn.fujitsu.com \
--to=yangx.jy@cn.fujitsu.com \
--cc=ltp@lists.linux.it \
/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