[PATCH v2 01/10] syscalls: fanotify: Add macro to require specific mark types

All of lore.kernel.org
 help / color / mirror / Atom feed

From: Gabriel Krisman Bertazi <krisman@collabora.com>
To: ltp@lists.linux.it, jack@suse.com, amir73il@gmail.com
Cc: khazhy@google.com, kernel@collabora.com,
	linux-ext4@vger.kernel.org, repnop@google.com,
	Gabriel Krisman Bertazi <krisman@collabora.com>
Subject: [PATCH v2 01/10] syscalls: fanotify: Add macro to require specific mark types
Date: Tue, 26 Oct 2021 15:42:30 -0300	[thread overview]
Message-ID: <20211026184239.151156-2-krisman@collabora.com> (raw)
In-Reply-To: <20211026184239.151156-1-krisman@collabora.com>

Like done for init flags and event types, and a macro to require a
specific mark type.

Signed-off-by: Gabriel Krisman Bertazi <krisman@collabora.com>
---
 testcases/kernel/syscalls/fanotify/fanotify.h | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/testcases/kernel/syscalls/fanotify/fanotify.h b/testcases/kernel/syscalls/fanotify/fanotify.h
index a2be183385e4..c67db3117e29 100644
--- a/testcases/kernel/syscalls/fanotify/fanotify.h
+++ b/testcases/kernel/syscalls/fanotify/fanotify.h
@@ -373,4 +373,9 @@ static inline int fanotify_mark_supported_by_kernel(uint64_t flag)
 	return rval;
 }
 
+#define REQUIRE_MARK_TYPE_SUPPORTED_ON_KERNEL(mark_type) do { \
+	fanotify_init_flags_err_msg(#mark_type, __FILE__, __LINE__, tst_brk_, \
+				    fanotify_mark_supported_by_kernel(mark_type)); \
+} while (0)
+
 #endif /* __FANOTIFY_H__ */
-- 
2.33.0

WARNING: multiple messages have this Message-ID (diff)

From: Gabriel Krisman Bertazi <krisman@collabora.com>
To: ltp@lists.linux.it, jack@suse.com, amir73il@gmail.com
Cc: linux-ext4@vger.kernel.org, kernel@collabora.com,
	Gabriel Krisman Bertazi <krisman@collabora.com>,
	khazhy@google.com, repnop@google.com
Subject: [LTP] [PATCH v2 01/10] syscalls: fanotify: Add macro to require specific mark types
Date: Tue, 26 Oct 2021 15:42:30 -0300	[thread overview]
Message-ID: <20211026184239.151156-2-krisman@collabora.com> (raw)
In-Reply-To: <20211026184239.151156-1-krisman@collabora.com>

Like done for init flags and event types, and a macro to require a
specific mark type.

Signed-off-by: Gabriel Krisman Bertazi <krisman@collabora.com>
---
 testcases/kernel/syscalls/fanotify/fanotify.h | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/testcases/kernel/syscalls/fanotify/fanotify.h b/testcases/kernel/syscalls/fanotify/fanotify.h
index a2be183385e4..c67db3117e29 100644
--- a/testcases/kernel/syscalls/fanotify/fanotify.h
+++ b/testcases/kernel/syscalls/fanotify/fanotify.h
@@ -373,4 +373,9 @@ static inline int fanotify_mark_supported_by_kernel(uint64_t flag)
 	return rval;
 }
 
+#define REQUIRE_MARK_TYPE_SUPPORTED_ON_KERNEL(mark_type) do { \
+	fanotify_init_flags_err_msg(#mark_type, __FILE__, __LINE__, tst_brk_, \
+				    fanotify_mark_supported_by_kernel(mark_type)); \
+} while (0)
+
 #endif /* __FANOTIFY_H__ */
-- 
2.33.0


-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

next prev parent reply	other threads:[~2021-10-26 18:43 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-26 18:42 [PATCH v2 00/10] Test the new fanotify FAN_FS_ERROR event Gabriel Krisman Bertazi
2021-10-26 18:42 ` [LTP] " Gabriel Krisman Bertazi
2021-10-26 18:42 ` Gabriel Krisman Bertazi [this message]
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-27  6:10     ` [LTP] " Amir Goldstein
2021-10-26 18:42 ` [PATCH v2 02/10] syscalls: fanotify: Add macro to require specific events Gabriel Krisman Bertazi
2021-10-26 18:42   ` [LTP] " Gabriel Krisman Bertazi
2021-10-27  6:23   ` Amir Goldstein
2021-10-27  6:23     ` [LTP] " Amir Goldstein
2021-10-26 18:42 ` [PATCH v2 03/10] syscalls/fanotify20: Introduce helpers for FAN_FS_ERROR test Gabriel Krisman Bertazi
2021-10-26 18:42   ` [LTP] " Gabriel Krisman Bertazi
2021-10-27  6:33   ` Amir Goldstein
2021-10-27  6:33     ` [LTP] " Amir Goldstein
2021-10-26 18:42 ` [PATCH v2 04/10] syscalls/fanotify20: Validate the generic error info Gabriel Krisman Bertazi
2021-10-26 18:42   ` [LTP] " Gabriel Krisman Bertazi
2021-10-27  6:43   ` Amir Goldstein
2021-10-27  6:43     ` [LTP] " Amir Goldstein
2021-10-27 10:19     ` Amir Goldstein
2021-10-27 10:19       ` [LTP] " Amir Goldstein
2021-10-26 18:42 ` [PATCH v2 05/10] syscalls/fanotify20: Validate incoming FID in FAN_FS_ERROR Gabriel Krisman Bertazi
2021-10-26 18:42   ` [LTP] " Gabriel Krisman Bertazi
2021-10-27  6:48   ` Amir Goldstein
2021-10-27  6:48     ` [LTP] " Amir Goldstein
2021-10-26 18:42 ` [PATCH v2 06/10] syscalls/fanotify20: Support submission of debugfs commands Gabriel Krisman Bertazi
2021-10-26 18:42   ` [LTP] " Gabriel Krisman Bertazi
2021-10-27  6:49   ` Amir Goldstein
2021-10-27  6:49     ` [LTP] " Amir Goldstein
2021-10-26 18:42 ` [PATCH v2 07/10] syscalls/fanotify20: Create a corrupted file Gabriel Krisman Bertazi
2021-10-26 18:42   ` [LTP] " Gabriel Krisman Bertazi
2021-10-27  6:51   ` Amir Goldstein
2021-10-27  6:51     ` [LTP] " Amir Goldstein
2021-10-26 18:42 ` [PATCH v2 08/10] syscalls/fanotify20: Test event after filesystem abort Gabriel Krisman Bertazi
2021-10-26 18:42   ` [LTP] " Gabriel Krisman Bertazi
2021-10-27  9:56   ` Amir Goldstein
2021-10-27  9:56     ` [LTP] " Amir Goldstein
2021-10-26 18:42 ` [PATCH v2 09/10] syscalls/fanotify20: Test file event with broken inode Gabriel Krisman Bertazi
2021-10-26 18:42   ` [LTP] " Gabriel Krisman Bertazi
2021-10-27  9:57   ` Amir Goldstein
2021-10-27  9:57     ` [LTP] " Amir Goldstein
2021-10-26 18:42 ` [PATCH v2 10/10] syscalls/fanotify20: Test capture of multiple errors Gabriel Krisman Bertazi
2021-10-26 18:42   ` [LTP] " Gabriel Krisman Bertazi
2021-10-27 10:00   ` Amir Goldstein
2021-10-27 10:00     ` [LTP] " Amir Goldstein
2021-10-29 15:03     ` Gabriel Krisman Bertazi
2021-10-29 15:03       ` [LTP] " Gabriel Krisman Bertazi

find likely ancestor, descendant, or conflicting patches for this message:
dfblob:a2be183385e dfblob:a2be183385e dfblob:c67db3117e2
dfblob:c67db3117e2
	(help)

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=20211026184239.151156-2-krisman@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 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.