From: Petr Vorel <pvorel@suse.cz>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Jan Kara <jack@suse.cz>,
ltp@lists.linux.it, Rhythm Mahajan <rhythm.m.mahajan@oracle.com>
Subject: Re: [LTP] [PATCH] fanotify01: fix test failure when running with nfs TMPDIR
Date: Mon, 17 Feb 2025 08:17:34 +0100 [thread overview]
Message-ID: <20250217071734.GA2298224@pevik> (raw)
In-Reply-To: <20250215091741.400782-1-amir73il@gmail.com>
Hi Amir,
> If TMPDIR does not support mount watches due to ENODEV, the failure
> to watch multiple fs would be EXDEV and not ENODEV.
> Reported-by: Rhythm Mahajan <rhythm.m.mahajan@oracle.com>
> Signed-off-by: Amir Goldstein <amir73il@gmail.com>
> ---
> testcases/kernel/syscalls/fanotify/fanotify01.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
> diff --git a/testcases/kernel/syscalls/fanotify/fanotify01.c b/testcases/kernel/syscalls/fanotify/fanotify01.c
> index c7e759166..38f5a0791 100644
> --- a/testcases/kernel/syscalls/fanotify/fanotify01.c
> +++ b/testcases/kernel/syscalls/fanotify/fanotify01.c
> @@ -375,8 +375,9 @@ static void setup(void)
> }
> if (fanotify_flags_supported_on_fs(FAN_REPORT_FID, FAN_MARK_MOUNT, FAN_OPEN, ".")) {
> - inode_mark_fid_xdev = errno;
> - tst_res(TINFO, "TMPDIR does not support reporting events with fid from multi fs");
> + inode_mark_fid_xdev = (errno == ENODEV) ? EXDEV : errno;
> + tst_res(TINFO, "TMPDIR does not support reporting events with fid from multi fs"
> + " (errno = %d)", errno);
I merged with LTP specific flag TERRNO which prints both string and numeric
value for errno:
tst_res(TINFO | TERRNO, "TMPDIR does not support reporting events with fid from multi fs");
Thanks for a fix!
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2025-02-17 7:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-15 9:17 [LTP] [PATCH] fanotify01: fix test failure when running with nfs TMPDIR Amir Goldstein
2025-02-17 7:17 ` 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=20250217071734.GA2298224@pevik \
--to=pvorel@suse.cz \
--cc=amir73il@gmail.com \
--cc=jack@suse.cz \
--cc=ltp@lists.linux.it \
--cc=rhythm.m.mahajan@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox