From: Matthew Bobrowski via ltp <ltp@lists.linux.it>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Jan Kara <jack@suse.cz>, ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 1/2] syscalls/fanotify14: Encode the expected errno in test case
Date: Wed, 20 Jul 2022 07:58:30 +1000 [thread overview]
Message-ID: <YtcpBkevcBF6iycz@google.com> (raw)
In-Reply-To: <20220719095853.3373732-2-amir73il@gmail.com>
On Tue, Jul 19, 2022 at 11:58:52AM +0200, Amir Goldstein wrote:
> So we can add test cases for errors other than EINVAL.
Just one optional nit. We can probably remove the comments which are
directly above the existing `if (errno == EINVAL)` checks as they're
specific to one expected errno value, but this is no longer the case
with ENOTDIR now in some fanotify_init/fanotify_mark cases.
Feel free to add RVB tags.
> Signed-off-by: Amir Goldstein <amir73il@gmail.com>
> ---
> .../kernel/syscalls/fanotify/fanotify14.c | 31 ++++++++++---------
> 1 file changed, 16 insertions(+), 15 deletions(-)
>
> diff --git a/testcases/kernel/syscalls/fanotify/fanotify14.c b/testcases/kernel/syscalls/fanotify/fanotify14.c
> index 5d74b9b91..c99e19706 100644
> --- a/testcases/kernel/syscalls/fanotify/fanotify14.c
> +++ b/testcases/kernel/syscalls/fanotify/fanotify14.c
> @@ -41,38 +41,39 @@ static struct test_case_t {
> unsigned int init_flags;
> unsigned int mark_flags;
> unsigned long long mask;
> + int expected_errno;
> } test_cases[] = {
> {
> - FAN_CLASS_CONTENT | FAN_REPORT_FID, 0, 0
> + FAN_CLASS_CONTENT | FAN_REPORT_FID, 0, 0, EINVAL
> },
> {
> - FAN_CLASS_PRE_CONTENT | FAN_REPORT_FID, 0, 0
> + FAN_CLASS_PRE_CONTENT | FAN_REPORT_FID, 0, 0, EINVAL
> },
> {
> - FAN_CLASS_NOTIF, 0, INODE_EVENTS
> + FAN_CLASS_NOTIF, 0, INODE_EVENTS, EINVAL
> },
> {
> - FAN_CLASS_NOTIF | FAN_REPORT_FID, FAN_MARK_MOUNT, INODE_EVENTS
> + FAN_CLASS_NOTIF | FAN_REPORT_FID, FAN_MARK_MOUNT, INODE_EVENTS, EINVAL
> },
> {
> /* FAN_REPORT_NAME without FAN_REPORT_DIR_FID is not valid */
> - FAN_CLASS_NOTIF | FAN_REPORT_NAME, 0, 0
> + FAN_CLASS_NOTIF | FAN_REPORT_NAME, 0, 0, EINVAL
> },
> {
> /* FAN_REPORT_NAME without FAN_REPORT_DIR_FID is not valid */
> - FAN_CLASS_NOTIF | FAN_REPORT_FID | FAN_REPORT_NAME, 0, 0
> + FAN_CLASS_NOTIF | FAN_REPORT_FID | FAN_REPORT_NAME, 0, 0, EINVAL
> },
> {
> /* FAN_REPORT_TARGET_FID without FAN_REPORT_FID is not valid */
> - FAN_CLASS_NOTIF | FAN_REPORT_TARGET_FID | FAN_REPORT_DFID_NAME, 0, 0
> + FAN_CLASS_NOTIF | FAN_REPORT_TARGET_FID | FAN_REPORT_DFID_NAME, 0, 0, EINVAL
> },
> {
> /* FAN_REPORT_TARGET_FID without FAN_REPORT_NAME is not valid */
> - FAN_CLASS_NOTIF | FAN_REPORT_TARGET_FID | FAN_REPORT_DFID_FID, 0, 0
> + FAN_CLASS_NOTIF | FAN_REPORT_TARGET_FID | FAN_REPORT_DFID_FID, 0, 0, EINVAL
> },
> {
> /* FAN_RENAME without FAN_REPORT_NAME is not valid */
> - FAN_CLASS_NOTIF | FAN_REPORT_DFID_FID, 0, FAN_RENAME
> + FAN_CLASS_NOTIF | FAN_REPORT_DFID_FID, 0, FAN_RENAME, EINVAL
> },
> };
>
> @@ -88,12 +89,12 @@ static void do_test(unsigned int number)
> * an invalid notification class is specified in
> * conjunction with FAN_REPORT_FID.
> */
> - if (errno == EINVAL) {
> + if (errno == tc->expected_errno) {
> tst_res(TPASS,
> "fanotify_fd=%d, fanotify_init(%x, O_RDONLY) "
> - "failed with error EINVAL as expected",
> + "failed with error %d as expected",
> fanotify_fd,
> - tc->init_flags);
> + tc->init_flags, tc->expected_errno);
> return;
> }
> tst_brk(TBROK | TERRNO,
> @@ -126,16 +127,16 @@ static void do_test(unsigned int number)
> * specified on the notification group, or using
> * INODE_EVENTS with mark type FAN_MARK_MOUNT.
> */
> - if (errno == EINVAL) {
> + if (errno == tc->expected_errno) {
> tst_res(TPASS,
> "ret=%d, fanotify_mark(%d, FAN_MARK_ADD | %x, "
> - "%llx, AT_FDCWD, %s) failed with error EINVAL "
> + "%llx, AT_FDCWD, %s) failed with error %d "
> "as expected",
> ret,
> fanotify_fd,
> tc->mark_flags,
> tc->mask,
> - FILE1);
> + FILE1, tc->expected_errno);
> goto out;
> }
> tst_brk(TBROK | TERRNO,
> --
> 2.25.1
>
/M
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2022-07-19 21:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-19 9:58 [LTP] [PATCH 0/2] Fanotify tests for v5.19-rc5 Amir Goldstein
2022-07-19 9:58 ` [LTP] [PATCH 1/2] syscalls/fanotify14: Encode the expected errno in test case Amir Goldstein
2022-07-19 21:58 ` Matthew Bobrowski via ltp [this message]
2022-07-20 10:53 ` Amir Goldstein
2022-07-25 12:49 ` Petr Vorel
2022-07-25 15:10 ` Amir Goldstein
2022-07-19 9:58 ` [LTP] [PATCH 2/2] syscalls/fanotify14: Add test cases for events not allowed on non-dir Amir Goldstein
2022-07-19 22:58 ` Matthew Bobrowski via ltp
2022-07-25 12:55 ` Petr Vorel
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=YtcpBkevcBF6iycz@google.com \
--to=ltp@lists.linux.it \
--cc=amir73il@gmail.com \
--cc=jack@suse.cz \
--cc=repnop@google.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.