Linux Test Project
 help / color / mirror / Atom feed
From: Amir Goldstein <amir73il@gmail.com>
To: Petr Vorel <pvorel@suse.cz>
Cc: Jan Kara <jack@suse.cz>,
	ltp@lists.linux.it, Rhythm Mahajan <rhythm.m.mahajan@oracle.com>
Subject: [LTP] [PATCH] fanotify01: fix test failure when running with nfs TMPDIR
Date: Sat, 15 Feb 2025 10:17:41 +0100	[thread overview]
Message-ID: <20250215091741.400782-1-amir73il@gmail.com> (raw)

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);
 	}
 }
 
-- 
2.34.1


-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

             reply	other threads:[~2025-02-15  9:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-15  9:17 Amir Goldstein [this message]
2025-02-17  7:17 ` [LTP] [PATCH] fanotify01: fix test failure when running with nfs TMPDIR 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=20250215091741.400782-1-amir73il@gmail.com \
    --to=amir73il@gmail.com \
    --cc=jack@suse.cz \
    --cc=ltp@lists.linux.it \
    --cc=pvorel@suse.cz \
    --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