From: Anand Suveer Jain <asj@kernel.org>
To: "Darrick J. Wong" <djwong@kernel.org>, Anand Jain <asj@kernel.org>
Cc: fstests@vger.kernel.org, linux-btrfs@vger.kernel.org,
linux-ext4@vger.kernel.org, linux-xfs@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net, zlang@redhat.com,
hch@infradead.org
Subject: Re: [PATCH v7 05/11] fstests: verify fanotify isolation on cloned filesystems
Date: Wed, 22 Jul 2026 06:36:47 +0800 [thread overview]
Message-ID: <1fb99189-bd69-4618-bd20-f64205159b1b@kernel.org> (raw)
In-Reply-To: <20260701171259.GG6517@frogsfrogsfrogs>
>> +. ./common/preamble
>> +
>> +_begin_fstest auto quick mount clone
>> +
>> +_require_test
>> +_require_block_device $TEST_DEV
>> +_require_loop
>> +_require_command "$FSNOTIFYWAIT_PROG" fsnotifywait
>> +_require_unique_f_fsid
>> +
>> +_cleanup()
>> +{
>> + cd /
>> + [[ -n $pid1 ]] && { kill -TERM "$pid1" 2> /dev/null; wait $pid1; }
>> + [[ -n $pid2 ]] && { kill -TERM "$pid2" 2> /dev/null; wait $pid2; }
>> +
>> + if [ "$semanage_added" = "yes" ]; then
>> + semanage permissive -d unconfined_t >/dev/null 2>&1 || true
>
> Needs to _require_command semanage, because it's not otherwise required
> by fstests. Otherwise looks ok to me.
>
Oh right. Added
In the new patch:
diff --git a/common/config b/common/config
::
+export SEMANAGE_PROG="$(type -P semanage)"
In this patch:
diff --git a/tests/generic/801 b/tests/generic/801
::
+_require_command "$SEMANAGE_PROG" semanage
next prev parent reply other threads:[~2026-07-21 22:36 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-17 11:20 [PATCH v7 0/11] fstests: add test coverage for cloned filesystem ids Anand Jain
2026-06-17 11:20 ` [PATCH v7 01/11] fstests: add _loop_image_create_clone() helper Anand Jain
2026-07-01 17:07 ` Darrick J. Wong
2026-07-21 22:38 ` Anand Suveer Jain
2026-06-17 11:20 ` [PATCH v7 02/11] fstests: add _clone_mount_option() helper Anand Jain
2026-06-17 11:20 ` [PATCH v7 03/11] fstests: add FSNOTIFYWAIT_PROG Anand Jain
2026-06-17 11:20 ` [PATCH v7 04/11] fstests: add _require_unique_f_fsid() helper Anand Jain
2026-07-01 17:11 ` Darrick J. Wong
2026-07-21 22:37 ` Anand Suveer Jain
2026-06-17 11:20 ` [PATCH v7 05/11] fstests: verify fanotify isolation on cloned filesystems Anand Jain
2026-07-01 17:12 ` Darrick J. Wong
2026-07-21 22:36 ` Anand Suveer Jain [this message]
2026-06-17 11:20 ` [PATCH v7 06/11] fstests: verify f_fsid for " Anand Jain
2026-07-01 17:33 ` Darrick J. Wong
2026-07-21 22:36 ` Anand Suveer Jain
2026-07-21 22:57 ` Darrick J. Wong
2026-07-21 23:21 ` Anand Suveer Jain
2026-07-21 23:25 ` Darrick J. Wong
2026-06-17 11:20 ` [PATCH v7 07/11] fstests: verify libblkid resolution of duplicate UUIDs Anand Jain
2026-06-17 11:20 ` [PATCH v7 08/11] fstests: verify IMA isolation on cloned filesystems Anand Jain
2026-06-17 11:20 ` [PATCH v7 09/11] fstests: verify exportfs file handles " Anand Jain
2026-06-17 11:20 ` [PATCH v7 10/11] fstests: add _change_metadata_uuid helper Anand Jain
2026-06-17 11:20 ` [PATCH v7 11/11] 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=1fb99189-bd69-4618-bd20-f64205159b1b@kernel.org \
--to=asj@kernel.org \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=hch@infradead.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--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