From: Petr Vorel <pvorel@suse.cz>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: ltp@lists.linux.it, mszeredi@redhat.com, brauner@kernel.org,
Jan Kara <jack@suse.cz>, Matthew Wilcox <willy@infradead.org>,
viro@zeniv.linux.org.uk, linux-fsdevel@vger.kernel.org
Subject: Re: [LTP] [PATCH v2 4/4] syscalls: splice07: New splice tst_fd iterator test
Date: Fri, 5 Jan 2024 00:11:09 +0100 [thread overview]
Message-ID: <20240104231109.GB1447350@pevik> (raw)
In-Reply-To: <20231016123320.9865-5-chrubis@suse.cz>
Hi Cyril,
...
> +++ b/testcases/kernel/syscalls/splice/splice07.c
> @@ -0,0 +1,85 @@
> +// SPDX-License-Identifier: GPL-2.0-or-later
> +
> +/*
> + * Copyright (C) 2023 Cyril Hrubis <chrubis@suse.cz>
> + */
> +
> +/*\
> + * [Description]
> + *
nit: missing a description.
> + */
> +#define _GNU_SOURCE
> +
> +#include <sys/socket.h>
> +#include <netinet/in.h>
> +
> +#include "tst_test.h"
> +
> +void check_splice(struct tst_fd *fd_in, struct tst_fd *fd_out)
nit: missing static
> + /* These produce EBADF instead of EINVAL */
> + switch (fd_out->type) {
> + case TST_FD_DIR:
> + case TST_FD_DEV_ZERO:
> + case TST_FD_PROC_MAPS:
> + case TST_FD_INOTIFY:
> + case TST_FD_PIPE_READ:
> + exp_errno = EBADF;
I tested it just on kernel 6.6. I wonder if this behaves the same on older
kernels.
> + default:
> + break;
> + }
> +
> + if (fd_in->type == TST_FD_PIPE_WRITE)
> + exp_errno = EBADF;
> +
> + if (fd_in->type == TST_FD_OPEN_TREE || fd_out->type == TST_FD_OPEN_TREE ||
> + fd_in->type == TST_FD_PATH || fd_out->type == TST_FD_PATH)
> + exp_errno = EBADF;
I suppose you'll send another version, which will make use of TST_EXP_FAIL.
https://lore.kernel.org/ltp/20240103115700.14585-1-chrubis@suse.cz/
BTW I also wonder if TST_EXP_FAIL() could simplify some of fanotify tests
(some of them got quite complex over time).
Reviewed-by: Petr Vorel <pvorel@suse.cz>
Kind regards,
Petr
prev parent reply other threads:[~2024-01-04 23:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-16 12:33 [PATCH v2 0/4] Add tst_fd iterator API Cyril Hrubis
2023-10-16 12:33 ` [PATCH v2 1/4] lib: Add tst_fd iterator Cyril Hrubis
2023-10-24 9:39 ` [LTP] " Richard Palethorpe
2024-01-05 0:42 ` Petr Vorel
2024-01-15 12:19 ` Cyril Hrubis
2024-01-15 22:52 ` Petr Vorel
2023-10-16 12:33 ` [PATCH v2 2/4] syscalls: readahead01: Make use of tst_fd Cyril Hrubis
2023-10-24 9:31 ` [LTP] " Richard Palethorpe
2023-10-16 12:33 ` [PATCH v2 3/4] syscalls: accept: Add tst_fd test Cyril Hrubis
2023-10-24 9:26 ` [LTP] " Richard Palethorpe
2023-10-24 9:34 ` Cyril Hrubis
2023-10-16 12:33 ` [PATCH v2 4/4] syscalls: splice07: New splice tst_fd iterator test Cyril Hrubis
2023-10-23 15:59 ` [LTP] " Richard Palethorpe
2023-10-24 7:56 ` Cyril Hrubis
2023-10-24 9:33 ` Jan Kara
2024-01-04 23:11 ` Petr Vorel [this message]
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=20240104231109.GB1447350@pevik \
--to=pvorel@suse.cz \
--cc=brauner@kernel.org \
--cc=chrubis@suse.cz \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=ltp@lists.linux.it \
--cc=mszeredi@redhat.com \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).