Linux Test Project
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Jan Kara <jack@suse.cz>,
	ltp@lists.linux.it, AnonymeMeow <anonymemeow@gmail.com>
Subject: Re: [LTP] [PATCH v2 2/2] fanotify13: fix test failure when running iterations
Date: Fri, 29 May 2026 18:34:20 +0200	[thread overview]
Message-ID: <20260529163420.GC294659@pevik> (raw)
In-Reply-To: <20260528162920.914321-2-amir73il@gmail.com>

Hi all,

it also fails on openSUSE Leap 42.2 due missing renameat2 (the same fix as for
musl described in previous email).

> +	if (tst_variant && (tc->mask & FAN_DELETE_SELF) &&
> +	    (!ovl_bind_mounted || rename_exchange_unsupported)) {
> +		/* The eviction of base fs inodes is defered due to overlay held reference */

While we are at it, we should fix old typo:
Typo: "defered" → "deferred".

Kind regards,
Petr

> +		tst_res(TCONF, "overlayfs base fs cannot be watched for delete self events");
> +		return;
> +	}
> +
>  	if (filesystem_mark_unsupported && mark->flag != FAN_MARK_INODE) {
>  		FANOTIFY_MARK_FLAGS_ERR_MSG(mark, filesystem_mark_unsupported);
>  		return;
> @@ -212,11 +220,6 @@ static void do_test(unsigned int number)
>  			tst_res(TCONF, "overlayfs base fs cannot be watched with mount mark");
>  			goto out;
>  		}
> -		if (tc->mask & FAN_DELETE_SELF) {
> -			/* The eviction of base fs inodes is defered due to overlay held reference */
> -			tst_res(TCONF, "overlayfs base fs cannot be watched for delete self events");
> -			goto out;
> -		}

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

  parent reply	other threads:[~2026-05-29 16:35 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-28 16:29 [LTP] [PATCH v2 1/2] fanotify21: fix test failure when running iterations Amir Goldstein
2026-05-28 16:29 ` [LTP] [PATCH v2 2/2] fanotify13: " Amir Goldstein
2026-05-29 16:30   ` Petr Vorel
2026-05-30 14:01     ` Amir Goldstein
2026-06-03 13:33       ` Petr Vorel
2026-05-29 16:34   ` Petr Vorel [this message]
2026-05-31 23:41   ` [LTP] [PATCH] " AnonymeMeow
2026-06-01  4:11     ` [LTP] " linuxtestproject.agent
2026-06-01  8:29     ` [LTP] [PATCH] " Amir Goldstein
2026-06-03  1:58       ` [LTP] [PATCH v2] " AnonymeMeow
2026-06-03  4:15         ` [LTP] " linuxtestproject.agent
2026-06-03 10:24         ` [LTP] [PATCH v2] " Amir Goldstein
2026-06-03 11:51           ` Petr Vorel
2026-05-28 18:43 ` [LTP] fanotify21: " linuxtestproject.agent
2026-05-29 16:25 ` [LTP] [PATCH v2 1/2] " 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=20260529163420.GC294659@pevik \
    --to=pvorel@suse.cz \
    --cc=amir73il@gmail.com \
    --cc=anonymemeow@gmail.com \
    --cc=jack@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