From: Christoph Hellwig <hch@infradead.org>
To: Anand Jain <anajain.sg@gmail.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Anand Jain <asj@kernel.org>,
fstests@vger.kernel.org, linux-btrfs@vger.kernel.org,
linux-ext4@vger.kernel.org, linux-xfs@vger.kernel.org,
amir73il@gmail.com, zlang@redhat.com
Subject: Re: [PATCH v5 03/10] fstests: add test for inotify isolation on cloned devices
Date: Tue, 26 May 2026 23:25:00 -0700 [thread overview]
Message-ID: <ahaOPOQYaE1wrbA6@infradead.org> (raw)
In-Reply-To: <e8d0caf9-df8b-415e-9f89-bc71e73a0e32@gmail.com>
On Tue, May 26, 2026 at 11:19:30PM +0800, Anand Jain wrote:
> > fanotity and inotify use exactly the same backends, so I'm not sure
> > why testing both matters.
>
> I noticed that back then I decided to keep both.
> Since fsnotifywait -F is only supported from kernel 5.1x.
> inotifywait serves the legacy LTS kernels where required.
< 5.1x is pretty old these days, I would not add test just for that.
> > Not that I care very strongly, I'm just a
> > bit confused.
>
> I am happy dropping inotifywait if unnecessary and confusing.
Not a major issue, but it felt weird.
next prev parent reply other threads:[~2026-05-27 6:25 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-21 12:54 [PATCH v5 0/10] fstests: add test coverage for cloned filesystem ids Anand Jain
2026-05-21 12:54 ` [PATCH v5 01/10] fstests: add _loop_image_create_clone() helper Anand Jain
2026-05-25 7:07 ` Christoph Hellwig
2026-05-21 12:54 ` [PATCH v5 02/10] fstests: add _clone_mount_option() helper Anand Jain
2026-05-25 7:07 ` Christoph Hellwig
2026-05-21 12:54 ` [PATCH v5 03/10] fstests: add test for inotify isolation on cloned devices Anand Jain
2026-05-25 7:09 ` Christoph Hellwig
2026-05-25 8:35 ` Anand Jain
2026-05-26 6:28 ` Christoph Hellwig
2026-05-26 15:19 ` Anand Jain
2026-05-27 6:25 ` Christoph Hellwig [this message]
2026-05-27 6:28 ` Anand Jain
2026-05-21 12:54 ` [PATCH v5 04/10] fstests: verify fanotify isolation on cloned filesystems Anand Jain
2026-05-25 7:11 ` Christoph Hellwig
2026-05-25 8:20 ` Anand Jain
2026-05-21 12:54 ` [PATCH v5 05/10] fstests: verify f_fsid for " Anand Jain
2026-05-25 7:13 ` Christoph Hellwig
2026-05-27 22:41 ` Anand Jain
2026-05-21 12:54 ` [PATCH v5 06/10] fstests: verify libblkid resolution of duplicate UUIDs Anand Jain
2026-05-21 12:54 ` [PATCH v5 07/10] fstests: verify IMA isolation on cloned filesystems Anand Jain
2026-05-21 12:54 ` [PATCH v5 08/10] fstests: verify exportfs file handles " Anand Jain
2026-05-21 12:54 ` [PATCH v5 09/10] fstests: add pre_clone_tune_uuid() healper Anand Jain
2026-05-21 13:10 ` Anand Jain
2026-05-25 7:14 ` Christoph Hellwig
2026-05-25 7:31 ` Anand Jain
2026-05-25 7:48 ` Christoph Hellwig
2026-05-21 12:55 ` [PATCH v5 10/10] fstests: test UUID consistency for clones with metadata_uuid Anand Jain
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=ahaOPOQYaE1wrbA6@infradead.org \
--to=hch@infradead.org \
--cc=amir73il@gmail.com \
--cc=anajain.sg@gmail.com \
--cc=asj@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=zlang@redhat.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