Re: [PATCH v2 10/10] syscalls/fanotify20: Test capture of multiple errors
From: Amir Goldstein <amir73il@gmail.com>
Date: 2021-10-27 10:01:09
Also in:
ltp
On Tue, Oct 26, 2021 at 9:44 PM Gabriel Krisman Bertazi [off-list ref] wrote:
When multiple FS errors occur, only the first is stored. This testcase validates this behavior by issuing two different errors and making sure only the first is stored, while the second is simply accumulated in error_count. Signed-off-by: Gabriel Krisman Bertazi <redacted>
Reviewed-by: Amir Goldstein <amir73il@gmail.com>
quoted hunk ↗ jump to hunk
--- .../kernel/syscalls/fanotify/fanotify20.c | 26 +++++++++++++++++++ 1 file changed, 26 insertions(+)diff --git a/testcases/kernel/syscalls/fanotify/fanotify20.c b/testcases/kernel/syscalls/fanotify/fanotify20.c index 7bcddcaa98cb..0083a018f2c6 100644 --- 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? Thanks, Amir.