From: Amir Goldstein <amir73il@gmail.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 0/5] Fanotify cleanup and test for v5.9 regression
Date: Fri, 4 Dec 2020 11:59:25 +0200 [thread overview]
Message-ID: <20201204095930.866421-1-amir73il@gmail.com> (raw)
Hi Petr,
Here are my followup patches to your great cleanup and
a new test for a bug fix that is already included in v5.9.y.
Note that I resurrected the helper from your V5 patches that
you turned into a macro following Cyril's comment.
I hope you both find the result satisfying.
There are no direct calls to fanotify_init() after those
cleanups (except for the intended use in fanotify14).
FYI, I have another test (inotify) for another v5.9 regression.
The fix is queued for upstream, but did reach upstream yet, so
I will post that test later.
Thanks,
Amir.
Amir Goldstein (5):
syscalls/fanotify: Generalize check for FAN_REPORT_FID support
syscalls/fanotify: Use generic checks for fanotify_init flags
syscalls/fanotify09: Read variable length events
syscalls/fanotify09: Add test case with two non-dir children
syscalls/fanotify09: Add test case for events with filename info
testcases/kernel/syscalls/fanotify/fanotify.h | 46 +++--
.../kernel/syscalls/fanotify/fanotify01.c | 4 +-
.../kernel/syscalls/fanotify/fanotify09.c | 167 +++++++++++++-----
.../kernel/syscalls/fanotify/fanotify10.c | 26 ++-
.../kernel/syscalls/fanotify/fanotify11.c | 21 +--
.../kernel/syscalls/fanotify/fanotify13.c | 2 +-
.../kernel/syscalls/fanotify/fanotify15.c | 2 +-
.../kernel/syscalls/fanotify/fanotify16.c | 14 +-
8 files changed, 180 insertions(+), 102 deletions(-)
--
2.25.1
next reply other threads:[~2020-12-04 9:59 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-04 9:59 Amir Goldstein [this message]
2020-12-04 9:59 ` [LTP] [PATCH 1/5] syscalls/fanotify: Generalize check for FAN_REPORT_FID support Amir Goldstein
2020-12-04 13:52 ` Petr Vorel
2020-12-07 10:48 ` Jan Kara
2020-12-04 9:59 ` [LTP] [PATCH 2/5] syscalls/fanotify: Use generic checks for fanotify_init flags Amir Goldstein
2020-12-04 13:55 ` Petr Vorel
2020-12-07 10:52 ` Jan Kara
2020-12-04 9:59 ` [LTP] [PATCH 3/5] syscalls/fanotify09: Read variable length events Amir Goldstein
2020-12-04 14:16 ` Petr Vorel
2020-12-07 10:55 ` Jan Kara
2020-12-07 11:44 ` Petr Vorel
2020-12-07 11:57 ` Petr Vorel
2020-12-07 14:07 ` Amir Goldstein
2020-12-07 14:22 ` Petr Vorel
2020-12-07 16:17 ` Amir Goldstein
2020-12-08 7:30 ` Petr Vorel
2020-12-04 9:59 ` [LTP] [PATCH 4/5] syscalls/fanotify09: Add test case with two non-dir children Amir Goldstein
2020-12-04 14:19 ` Petr Vorel
2020-12-07 11:01 ` Jan Kara
2020-12-04 9:59 ` [LTP] [PATCH 5/5] syscalls/fanotify09: Add test case for events with filename info Amir Goldstein
2020-12-04 14:22 ` Petr Vorel
2020-12-07 11:11 ` Jan Kara
2020-12-04 14:27 ` [LTP] [PATCH 0/5] Fanotify cleanup and test for v5.9 regression Petr Vorel
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=20201204095930.866421-1-amir73il@gmail.com \
--to=amir73il@gmail.com \
--cc=ltp@lists.linux.it \
/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