From: Gabriel Krisman Bertazi <krisman@collabora.com>
To: Amir Goldstein <amir73il@gmail.com>
Cc: kernel@collabora.com, Khazhismel Kumykov <khazhy@google.com>,
Matthew Bobrowski <repnop@google.com>, Jan Kara <jack@suse.com>,
Ext4 <linux-ext4@vger.kernel.org>, LTP List <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH v2 10/10] syscalls/fanotify20: Test capture of multiple errors
Date: Fri, 29 Oct 2021 12:03:11 -0300 [thread overview]
Message-ID: <87bl37an68.fsf@collabora.com> (raw)
In-Reply-To: <CAOQ4uxia5Qhieui+keBLumWwGd2+wv88+FykWq-zMrDrHmZUrA@mail.gmail.com> (Amir Goldstein's message of "Wed, 27 Oct 2021 13:00:07 +0300")
Amir Goldstein <amir73il@gmail.com> writes:
> On Tue, Oct 26, 2021 at 9:44 PM Gabriel Krisman Bertazi
>> --- a/testcases/kernel/syscalls/fanotify/fanotify20.c
>> +++ b/testcases/kernel/syscalls/fanotify/fanotify20.c
>> @@ -78,6 +78,18 @@ static void tcase2_trigger_lookup(void)
>> ret, BAD_DIR, errno, EUCLEAN);
>> }
>>
>> +static void tcase3_trigger(void)
>> +{
>> + trigger_fs_abort();
>> + tcase2_trigger_lookup();
>
> So after remount,abort filesystem operations can still be executed?
> Then I guess my comment from the previous patch about running the test in a loop
> is not relevant?
Hi Amir,
As you mentioned here, -i works fine. Abort will remount with
MS_RDONLY, and this doesn't affect the existing tests. Future tests
that write to the file system inside .trigger_error() would require the
umount-mount cycle but, since the goal is testing fanotify and not
specific fs errors, I think we don't need the added complexity of such
tests.
Output of '-i #' always pass:
root@test-box:~/ltp/testcases/kernel/syscalls/fanotify# ./fanotify20 -i 5
tst_device.c:88: TINFO: Found free device 0 '/dev/loop0'
tst_test.c:932: TINFO: Formatting /dev/loop0 with ext4 opts='' extra opts=''
mke2fs 1.46.4 (18-Aug-2021)
tst_test.c:1363: TINFO: Timeout per run is 0h 05m 00s
fanotify.h:252: TINFO: fid(test_mnt) = 469af9fc.8ced5767.2.0.0...
fanotify.h:252: TINFO: fid(test_mnt/internal_dir/bad_dir) = 469af9fc.8ced5767.8002.acd05469.0...
debugfs 1.46.4 (18-Aug-2021)
fanotify20.c:234: TPASS: Successfully received: Trigger abort
fanotify20.c:234: TPASS: Successfully received: Lookup of inode with invalid mode
fanotify20.c:234: TPASS: Successfully received: Multiple error submission
fanotify20.c:234: TPASS: Successfully received: Multiple error submission 2
fanotify20.c:234: TPASS: Successfully received: Trigger abort
fanotify20.c:234: TPASS: Successfully received: Lookup of inode with invalid mode
fanotify20.c:234: TPASS: Successfully received: Multiple error submission
fanotify20.c:234: TPASS: Successfully received: Multiple error submission 2
fanotify20.c:234: TPASS: Successfully received: Trigger abort
fanotify20.c:234: TPASS: Successfully received: Lookup of inode with invalid mode
fanotify20.c:234: TPASS: Successfully received: Multiple error submission
fanotify20.c:234: TPASS: Successfully received: Multiple error submission 2
fanotify20.c:234: TPASS: Successfully received: Trigger abort
fanotify20.c:234: TPASS: Successfully received: Lookup of inode with invalid mode
fanotify20.c:234: TPASS: Successfully received: Multiple error submission
fanotify20.c:234: TPASS: Successfully received: Multiple error submission 2
fanotify20.c:234: TPASS: Successfully received: Trigger abort
fanotify20.c:234: TPASS: Successfully received: Lookup of inode with invalid mode
fanotify20.c:234: TPASS: Successfully received: Multiple error submission
fanotify20.c:234: TPASS: Successfully received: Multiple error submission 2
Summary:
passed 20
failed 0
broken 0
skipped 0
warnings 0
Thanks,
--
Gabriel Krisman Bertazi
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2021-10-29 15:03 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 18:42 [LTP] [PATCH v2 00/10] Test the new fanotify FAN_FS_ERROR event Gabriel Krisman Bertazi
2021-10-26 18:42 ` [LTP] [PATCH v2 01/10] syscalls: fanotify: Add macro to require specific mark types Gabriel Krisman Bertazi
2021-10-27 6:10 ` Amir Goldstein
2021-10-26 18:42 ` [LTP] [PATCH v2 02/10] syscalls: fanotify: Add macro to require specific events Gabriel Krisman Bertazi
2021-10-27 6:23 ` Amir Goldstein
2021-10-26 18:42 ` [LTP] [PATCH v2 03/10] syscalls/fanotify20: Introduce helpers for FAN_FS_ERROR test Gabriel Krisman Bertazi
2021-10-27 6:33 ` Amir Goldstein
2021-10-26 18:42 ` [LTP] [PATCH v2 04/10] syscalls/fanotify20: Validate the generic error info Gabriel Krisman Bertazi
2021-10-27 6:43 ` Amir Goldstein
2021-10-27 10:19 ` Amir Goldstein
2021-10-26 18:42 ` [LTP] [PATCH v2 05/10] syscalls/fanotify20: Validate incoming FID in FAN_FS_ERROR Gabriel Krisman Bertazi
2021-10-27 6:48 ` Amir Goldstein
2021-10-26 18:42 ` [LTP] [PATCH v2 06/10] syscalls/fanotify20: Support submission of debugfs commands Gabriel Krisman Bertazi
2021-10-27 6:49 ` Amir Goldstein
2021-10-26 18:42 ` [LTP] [PATCH v2 07/10] syscalls/fanotify20: Create a corrupted file Gabriel Krisman Bertazi
2021-10-27 6:51 ` Amir Goldstein
2021-10-26 18:42 ` [LTP] [PATCH v2 08/10] syscalls/fanotify20: Test event after filesystem abort Gabriel Krisman Bertazi
2021-10-27 9:56 ` Amir Goldstein
2021-10-26 18:42 ` [LTP] [PATCH v2 09/10] syscalls/fanotify20: Test file event with broken inode Gabriel Krisman Bertazi
2021-10-27 9:57 ` Amir Goldstein
2021-10-26 18:42 ` [LTP] [PATCH v2 10/10] syscalls/fanotify20: Test capture of multiple errors Gabriel Krisman Bertazi
2021-10-27 10:00 ` Amir Goldstein
2021-10-29 15:03 ` Gabriel Krisman Bertazi [this message]
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=87bl37an68.fsf@collabora.com \
--to=krisman@collabora.com \
--cc=amir73il@gmail.com \
--cc=jack@suse.com \
--cc=kernel@collabora.com \
--cc=khazhy@google.com \
--cc=linux-ext4@vger.kernel.org \
--cc=ltp@lists.linux.it \
--cc=repnop@google.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;
as well as URLs for NNTP newsgroup(s).