From: Richard Palethorpe <rpalethorpe@suse.de>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
Miklos Szeredi <miklos@szeredi.hu>,
linux-unionfs@vger.kernel.org, ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 1/3] fanotify13: Test watching overlayfs upper fs
Date: Thu, 14 Sep 2023 11:32:39 +0100 [thread overview]
Message-ID: <87il8dghw0.fsf@suse.de> (raw)
In-Reply-To: <20230903111558.2603332-2-amir73il@gmail.com>
Hello Amir,
Amir Goldstein <amir73il@gmail.com> writes:
> Run a test variant with overlayfs (over all supported fs)
> when watching the upper fs.
>
> This is a regression test for kernel fix bc2473c90fca
> ("ovl: enable fsnotify events on underlying real files"),
> from kernel 6.5, which is not likely to be backported to older kernels.
>
> To avoid waiting for events that won't arrive when testing old kernels,
> require that kernel supports encoding fid with new flag AT_HADNLE_FID,
> also merged to 6.5 and not likely to be backported to older kernels.
Unfortunately Petr's not here at the moment.
I guess this first patch doesn't require 6.6? So it could be merged
independently without further considerations for what makes it into 6.6?
--
Thank you,
Richard.
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2023-09-14 10:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-03 11:15 [LTP] [PATCH 0/3] Tests for fanotify and overlayfs Amir Goldstein
2023-09-03 11:15 ` [LTP] [PATCH 1/3] fanotify13: Test watching overlayfs upper fs Amir Goldstein
2023-09-14 10:32 ` Richard Palethorpe [this message]
2023-09-14 13:24 ` Amir Goldstein
2023-09-15 6:51 ` Petr Vorel
2023-09-15 8:28 ` Cyril Hrubis
2023-09-15 9:02 ` Petr Vorel
2023-09-03 11:15 ` [LTP] [PATCH 2/3] fanotify13: Test watching overlayfs with FAN_REPORT_FID Amir Goldstein
2023-09-03 11:15 ` [LTP] [PATCH 3/3] fanotify13: Test unique overlayfs fsid Amir Goldstein
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=87il8dghw0.fsf@suse.de \
--to=rpalethorpe@suse.de \
--cc=amir73il@gmail.com \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-unionfs@vger.kernel.org \
--cc=ltp@lists.linux.it \
--cc=miklos@szeredi.hu \
/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