From: Petr Vorel <pvorel@suse.cz> To: Gabriel Krisman Bertazi <krisman@collabora.com> Cc: Amir Goldstein <amir73il@gmail.com>, Jan Kara <jack@suse.com>, Matthew Bobrowski <repnop@google.com>, Ext4 <linux-ext4@vger.kernel.org>, kernel@collabora.com, Khazhismel Kumykov <khazhy@google.com>, LTP List <ltp@lists.linux.it> Subject: Re: [PATCH v4 0/9] Test the new fanotify FAN_FS_ERROR event Date: Mon, 22 Nov 2021 08:47:41 +0100 [thread overview] Message-ID: <YZtLDXW01Cz0BfPU@pevik> (raw) In-Reply-To: <8735nsuepi.fsf@collabora.com> Hi all, <snip> > Hi Amir, > I have pushed v4 to : > https://gitlab.collabora.com/krisman/ltp.git -b fan-fs-error_v4 FYI I've rebased it on my fix 3b2ea2e00 ("configure.ac: Add struct fanotify_event_info_pidfd check") https://github.com/linux-test-project/ltp.git -b gertazi/fanotify21.v4.fixes diff to krisman/fan-fs-error_v4: diff --git configure.ac configure.ac index a9dc25249..d25183368 100644 --- configure.ac +++ configure.ac @@ -160,8 +160,8 @@ AC_CHECK_MEMBERS([struct utsname.domainname],,,[ AC_CHECK_TYPES([enum kcmp_type],,,[#include <linux/kcmp.h>]) AC_CHECK_TYPES([struct acct_v3],,,[#include <sys/acct.h>]) AC_CHECK_TYPES([struct af_alg_iv, struct sockaddr_alg],,,[# include <linux/if_alg.h>]) -AC_CHECK_TYPES([struct fanotify_event_info_fid, struct fanotify_event_info_header, - struct fanotify_event_info_error],[],[],[#include <sys/fanotify.h>]) +AC_CHECK_TYPES([struct fanotify_event_info_fid, struct fanotify_event_info_error, + struct fanotify_event_info_header, struct fanotify_event_info_pidfd],,,[#include <sys/fanotify.h>]) AC_CHECK_TYPES([struct file_dedupe_range],,,[#include <linux/fs.h>]) AC_CHECK_TYPES([struct file_handle],,,[ Kind regards, Petr
WARNING: multiple messages have this Message-ID (diff)
From: Petr Vorel <pvorel@suse.cz> To: Gabriel Krisman Bertazi <krisman@collabora.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 v4 0/9] Test the new fanotify FAN_FS_ERROR event Date: Mon, 22 Nov 2021 08:47:41 +0100 [thread overview] Message-ID: <YZtLDXW01Cz0BfPU@pevik> (raw) In-Reply-To: <8735nsuepi.fsf@collabora.com> Hi all, <snip> > Hi Amir, > I have pushed v4 to : > https://gitlab.collabora.com/krisman/ltp.git -b fan-fs-error_v4 FYI I've rebased it on my fix 3b2ea2e00 ("configure.ac: Add struct fanotify_event_info_pidfd check") https://github.com/linux-test-project/ltp.git -b gertazi/fanotify21.v4.fixes diff to krisman/fan-fs-error_v4: diff --git configure.ac configure.ac index a9dc25249..d25183368 100644 --- configure.ac +++ configure.ac @@ -160,8 +160,8 @@ AC_CHECK_MEMBERS([struct utsname.domainname],,,[ AC_CHECK_TYPES([enum kcmp_type],,,[#include <linux/kcmp.h>]) AC_CHECK_TYPES([struct acct_v3],,,[#include <sys/acct.h>]) AC_CHECK_TYPES([struct af_alg_iv, struct sockaddr_alg],,,[# include <linux/if_alg.h>]) -AC_CHECK_TYPES([struct fanotify_event_info_fid, struct fanotify_event_info_header, - struct fanotify_event_info_error],[],[],[#include <sys/fanotify.h>]) +AC_CHECK_TYPES([struct fanotify_event_info_fid, struct fanotify_event_info_error, + struct fanotify_event_info_header, struct fanotify_event_info_pidfd],,,[#include <sys/fanotify.h>]) AC_CHECK_TYPES([struct file_dedupe_range],,,[#include <linux/fs.h>]) AC_CHECK_TYPES([struct file_handle],,,[ Kind regards, Petr -- Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2021-11-22 7:47 UTC|newest] Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-18 23:57 [PATCH v4 0/9] Test the new fanotify FAN_FS_ERROR event Gabriel Krisman Bertazi 2021-11-18 23:57 ` [LTP] " Gabriel Krisman Bertazi 2021-11-18 23:57 ` [PATCH v4 1/9] syscalls: fanotify: Add macro to require specific mark types Gabriel Krisman Bertazi 2021-11-18 23:57 ` [LTP] " Gabriel Krisman Bertazi 2021-11-18 23:57 ` [PATCH v4 2/9] syscalls: fanotify: Add macro to require specific events Gabriel Krisman Bertazi 2021-11-18 23:57 ` [LTP] " Gabriel Krisman Bertazi 2021-11-18 23:57 ` [PATCH v4 3/9] syscalls/fanotify22: Introduce FAN_FS_ERROR test Gabriel Krisman Bertazi 2021-11-18 23:57 ` [LTP] " Gabriel Krisman Bertazi 2021-11-18 23:57 ` [PATCH v4 4/9] syscalls/fanotify22: Validate the generic error info Gabriel Krisman Bertazi 2021-11-18 23:57 ` [LTP] " Gabriel Krisman Bertazi 2021-11-19 5:38 ` Amir Goldstein 2021-11-19 5:38 ` [LTP] " Amir Goldstein 2021-11-19 19:29 ` Petr Vorel 2021-11-19 19:29 ` [LTP] " Petr Vorel 2021-11-19 22:39 ` Petr Vorel 2021-11-19 22:39 ` [LTP] " Petr Vorel 2021-11-18 23:57 ` [PATCH v4 5/9] syscalls/fanotify22: Validate incoming FID in FAN_FS_ERROR Gabriel Krisman Bertazi 2021-11-18 23:57 ` [LTP] " Gabriel Krisman Bertazi 2021-11-18 23:57 ` [PATCH v4 6/9] syscalls/fanotify22: Support submission of debugfs commands Gabriel Krisman Bertazi 2021-11-18 23:57 ` [LTP] " Gabriel Krisman Bertazi 2021-11-18 23:57 ` [PATCH v4 7/9] syscalls/fanotify22: Create a corrupted file Gabriel Krisman Bertazi 2021-11-18 23:57 ` [LTP] " Gabriel Krisman Bertazi 2021-11-18 23:57 ` [PATCH v4 8/9] syscalls/fanotify22: Test file event with broken inode Gabriel Krisman Bertazi 2021-11-18 23:57 ` [LTP] " Gabriel Krisman Bertazi 2021-11-18 23:57 ` [PATCH v4 9/9] syscalls/fanotify22: Test capture of multiple errors Gabriel Krisman Bertazi 2021-11-18 23:57 ` [LTP] " Gabriel Krisman Bertazi 2021-11-19 5:48 ` [PATCH v4 0/9] Test the new fanotify FAN_FS_ERROR event Amir Goldstein 2021-11-19 5:48 ` [LTP] " Amir Goldstein 2021-11-19 19:29 ` Gabriel Krisman Bertazi 2021-11-19 19:29 ` [LTP] " Gabriel Krisman Bertazi 2021-11-20 10:43 ` Amir Goldstein 2021-11-20 10:43 ` [LTP] " Amir Goldstein 2021-11-22 7:47 ` Petr Vorel [this message] 2021-11-22 7:47 ` Petr Vorel 2021-11-22 17:35 ` Gabriel Krisman Bertazi 2021-11-22 17:35 ` [LTP] " Gabriel Krisman Bertazi 2021-11-22 21:09 ` Petr Vorel 2021-11-22 21:09 ` [LTP] " Petr Vorel 2021-11-24 10:39 ` Petr Vorel 2021-11-24 10:39 ` Petr Vorel 2021-12-20 11:48 ` Amir Goldstein 2021-12-20 11:48 ` Amir Goldstein 2021-12-20 18:07 ` Petr Vorel 2021-12-20 18:07 ` Petr Vorel 2022-01-10 15:16 ` Petr Vorel 2022-01-10 15:16 ` [LTP] " Petr Vorel 2022-02-02 13:49 ` Amir Goldstein 2022-02-02 13:49 ` [LTP] " Amir Goldstein 2022-02-02 14:10 ` Jan Stancek 2022-02-02 14:10 ` Jan Stancek 2022-02-02 16:45 ` Gabriel Krisman Bertazi 2022-02-02 16:45 ` Gabriel Krisman Bertazi 2022-02-02 14:22 ` Petr Vorel 2022-02-02 14:22 ` [LTP] " Petr Vorel 2022-02-02 16:13 ` Cyril Hrubis 2022-02-02 16:13 ` Cyril Hrubis 2022-02-02 16:57 ` Petr Vorel 2022-02-02 16:57 ` 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=YZtLDXW01Cz0BfPU@pevik \ --to=pvorel@suse.cz \ --cc=amir73il@gmail.com \ --cc=jack@suse.com \ --cc=kernel@collabora.com \ --cc=khazhy@google.com \ --cc=krisman@collabora.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.