From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v4 1/2] syscalls/splice04: add test for splice() from pipe to pipe
Date: Fri, 19 May 2017 16:25:42 +0200 [thread overview]
Message-ID: <20170519142542.GD17258@rei.lan> (raw)
In-Reply-To: <1494580475-3522-1-git-send-email-bxue@redhat.com>
Hi!
> +#define _GNU_SOURCE
> +#include <fcntl.h>
> +#include <stdlib.h>
> +#include "tst_test.h"
> +
> +#define PIPE_MAX (64*1024)
> +
> +static char *str_len_data;
> +static int num_len_data = PIPE_MAX;
> +static char *arr_in, *arr_out;
> +
> +static struct tst_option options[] = {
> + {"l:", &str_len_data, "-l <num> Length of test data (in bytes)"},
> + {NULL, NULL, NULL},
> +};
> +
> +static void setup(void)
> +{
> + int i, pipe_max_unpriv, pipe_limit;
> +
> + SAFE_FILE_SCANF("/proc/sys/fs/pipe-max-size", "%d", &pipe_max_unpriv);
> + pipe_limit = pipe_max_unpriv < num_len_data ? pipe_max_unpriv :
> + num_len_data;
Hmm, this is case for a MIN() macro. I guess that I should add MIN() and
MAX*() to the tst_test.h header since we have several uses in the
testcases already.
> + num_len_data = pipe_limit;
> +
> + if (tst_parse_int(str_len_data, &num_len_data, 1, pipe_limit))
> + tst_brk(TBROK, "Invalid length of data: '%s', "
> + "valid value: [1, %d]", str_len_data, pipe_limit);
There should be curly braces around the multiline statement.
> + tst_res(TINFO, "splice size = %d", num_len_data);
> + arr_in = SAFE_MALLOC(num_len_data);
> + arr_out = SAFE_MALLOC(num_len_data);
> + for (i = 0; i < num_len_data; i++)
> + arr_in[i] = i & 0xff;
> +}
> +
> +static void cleanup(void)
> +{
> + free(arr_in);
> + free(arr_out);
> +}
> +
> +static void pipe_pipe(void)
> +{
> + int pp1[2], pp2[2], i, ret;
> +
> + SAFE_PIPE(pp1);
> + SAFE_PIPE(pp2);
> + SAFE_WRITE(1, pp1[1], arr_in, num_len_data);
> + for (i = 0; i < num_len_data; i++) {
> + ret = splice(pp1[0], NULL, pp2[1], NULL, 1, SPLICE_F_MOVE);
> + if (ret == -1) {
> + tst_res(TFAIL | TERRNO, "splice error");
> + goto exit;
> + }
> + SAFE_READ(1, pp2[0], arr_out + i, 1);
> + }
I do not understand why we are moving the data byte by byte here?
And also the SPLICE_F_MOVE flag, even if that was correctly implemented,
would be useless here.
> + for (i = 0; i < num_len_data; i++) {
> + if (arr_in[i] != arr_out[i]) {
> + tst_res(TFAIL, "wrong data at %d: expected: %d, "
> + "actual: %d", i, arr_in[i], arr_out[i]);
> + goto exit;
> + }
> + }
> + tst_res(TPASS, "splice(2) from pipe to pipe run pass.");
> +
> +exit:
> + SAFE_CLOSE(pp1[1]);
> + SAFE_CLOSE(pp1[0]);
> + SAFE_CLOSE(pp2[1]);
> + SAFE_CLOSE(pp2[0]);
> +}
> +
> +static struct tst_test test = {
> + .tid = "splice04",
> + .test_all = pipe_pipe,
> + .setup = setup,
> + .cleanup = cleanup,
> + .options = options,
> + .min_kver = "2.6.31"
> +};
> --
> 1.8.3.1
>
>
> --
> Mailing list info: https://lists.linux.it/listinfo/ltp
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2017-05-19 14:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-12 9:14 [LTP] [PATCH v4 1/2] syscalls/splice04: add test for splice() from pipe to pipe bxue
2017-05-12 9:14 ` [LTP] [PATCH v4 2/2] syscalls/splice05: add test for splice() between pipe and socket bxue
2017-05-19 14:27 ` Cyril Hrubis
2017-05-19 14:25 ` Cyril Hrubis [this message]
2017-05-19 14:38 ` [LTP] [PATCH v4 1/2] syscalls/splice04: add test for splice() from pipe to pipe 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=20170519142542.GD17258@rei.lan \
--to=chrubis@suse.cz \
--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