From: Jan Kara <jack@suse.cz>
To: Gabriel Krisman Bertazi <krisman@collabora.com>
Cc: Guenter Roeck <linux@roeck-us.net>,
jack@suse.com, amir73il@gmail.com, djwong@kernel.org,
tytso@mit.edu, david@fromorbit.com, dhowells@redhat.com,
khazhy@google.com, linux-fsdevel@vger.kernel.org,
linux-ext4@vger.kernel.org, linux-api@vger.kernel.org,
kernel@collabora.com
Subject: Re: [PATCH v8 31/32] samples: Add fs error monitoring example
Date: Mon, 1 Nov 2021 12:42:22 +0100 [thread overview]
Message-ID: <20211101114222.GA21679@quack2.suse.cz> (raw)
In-Reply-To: <87fsslasgz.fsf@collabora.com>
On Thu 28-10-21 15:56:28, Gabriel Krisman Bertazi wrote:
> Guenter Roeck <linux@roeck-us.net> writes:
>
> > On Mon, Oct 18, 2021 at 09:00:14PM -0300, Gabriel Krisman Bertazi wrote:
> >> Introduce an example of a FAN_FS_ERROR fanotify user to track filesystem
> >> errors.
> >>
> >> Reviewed-by: Amir Goldstein <amir73il@gmail.com>
> >> Signed-off-by: Gabriel Krisman Bertazi <krisman@collabora.com>
> >> Reviewed-by: Jan Kara <jack@suse.cz>
> >> ---
> >> Changes since v4:
> >> - Protect file_handle defines with ifdef guards
> >>
> >> Changes since v1:
> >> - minor fixes
> >> ---
> >> samples/Kconfig | 9 +++
> >> samples/Makefile | 1 +
> >> samples/fanotify/Makefile | 5 ++
> >> samples/fanotify/fs-monitor.c | 142 ++++++++++++++++++++++++++++++++++
> >> 4 files changed, 157 insertions(+)
> >> create mode 100644 samples/fanotify/Makefile
> >> create mode 100644 samples/fanotify/fs-monitor.c
> >>
> >> diff --git a/samples/Kconfig b/samples/Kconfig
> >> index b0503ef058d3..88353b8eac0b 100644
> >> --- a/samples/Kconfig
> >> +++ b/samples/Kconfig
> >> @@ -120,6 +120,15 @@ config SAMPLE_CONNECTOR
> >> with it.
> >> See also Documentation/driver-api/connector.rst
> >>
> >> +config SAMPLE_FANOTIFY_ERROR
> >> + bool "Build fanotify error monitoring sample"
> >> + depends on FANOTIFY
> >
> > This needs something like
> > depends on CC_CAN_LINK
> > or possibly even
> > depends on CC_CAN_LINK && HEADERS_INSTALL
> > to avoid compilation errors such as
> >
> > samples/fanotify/fs-monitor.c:7:10: fatal error: errno.h: No such file or directory
> > 7 | #include <errno.h>
> > | ^~~~~~~~~
> > compilation terminated.
> >
> > when using a toolchain without C library support, such as those provided
> > on kernel.org.
>
> Thank you, Guenter.
>
> We discussed this, but I wasn't sure how to silence the error and it
> didn't trigger in the past versions.
>
> The original patch is already in Jan's tree. Jan, would you pick the
> pack below to address it? Feel free to squash it into the original
> commit, if you think it is saner..
Thanks guys, I've added the patch to my tree. If we had more time, I'd
probably squash it but given I'd like to send Linus a pull request at the
end of the week I don't want to touch commits that are already in next.
Honza
> -- >8 --
> From: Gabriel Krisman Bertazi <krisman@collabora.com>
> Date: Thu, 28 Oct 2021 15:34:46 -0300
> Subject: [PATCH] samples: Make fs-monitor depend on libc and headers
>
> Prevent build errors when headers or libc are not available, such as on
> kernel build bots, like the below:
>
> samples/fanotify/fs-monitor.c:7:10: fatal error: errno.h: No such file
> or directory
> 7 | #include <errno.h>
> | ^~~~~~~~~
>
> Suggested-by: Guenter Roeck <linux@roeck-us.net>
> Signed-off-by: Gabriel Krisman Bertazi <krisman@collabora.com>
> ---
> samples/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/samples/Kconfig b/samples/Kconfig
> index 88353b8eac0b..56539b21f2c7 100644
> --- a/samples/Kconfig
> +++ b/samples/Kconfig
> @@ -122,7 +122,7 @@ config SAMPLE_CONNECTOR
>
> config SAMPLE_FANOTIFY_ERROR
> bool "Build fanotify error monitoring sample"
> - depends on FANOTIFY
> + depends on FANOTIFY && CC_CAN_LINK && HEADERS_INSTALL
> help
> When enabled, this builds an example code that uses the
> FAN_FS_ERROR fanotify mechanism to monitor filesystem
> --
> 2.33.0
>
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2021-11-01 11:42 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-18 23:59 [PATCH v8 00/32] file system-wide error monitoring Gabriel Krisman Bertazi
2021-10-18 23:59 ` [PATCH v8 01/32] fsnotify: pass data_type to fsnotify_name() Gabriel Krisman Bertazi
2021-10-18 23:59 ` [PATCH v8 02/32] fsnotify: pass dentry instead of inode data Gabriel Krisman Bertazi
2021-10-18 23:59 ` [PATCH v8 03/32] fsnotify: clarify contract for create event hooks Gabriel Krisman Bertazi
2021-10-18 23:59 ` [PATCH v8 04/32] fsnotify: Don't insert unmergeable events in hashtable Gabriel Krisman Bertazi
2021-10-18 23:59 ` [PATCH v8 05/32] fanotify: Fold event size calculation to its own function Gabriel Krisman Bertazi
2021-10-18 23:59 ` [PATCH v8 06/32] fanotify: Split fsid check from other fid mode checks Gabriel Krisman Bertazi
2021-10-18 23:59 ` [PATCH v8 07/32] inotify: Don't force FS_IN_IGNORED Gabriel Krisman Bertazi
2021-10-18 23:59 ` [PATCH v8 08/32] fsnotify: Add helper to detect overflow_event Gabriel Krisman Bertazi
2021-10-18 23:59 ` [PATCH v8 09/32] fsnotify: Add wrapper around fsnotify_add_event Gabriel Krisman Bertazi
2021-10-18 23:59 ` [PATCH v8 10/32] fsnotify: Retrieve super block from the data field Gabriel Krisman Bertazi
2021-10-18 23:59 ` [PATCH v8 11/32] fsnotify: Protect fsnotify_handle_inode_event from no-inode events Gabriel Krisman Bertazi
2021-10-19 5:34 ` Amir Goldstein
2021-10-19 10:01 ` Jan Kara
2021-10-18 23:59 ` [PATCH v8 12/32] fsnotify: Pass group argument to free_event Gabriel Krisman Bertazi
2021-10-18 23:59 ` [PATCH v8 13/32] fanotify: Support null inode event in fanotify_dfid_inode Gabriel Krisman Bertazi
2021-10-18 23:59 ` [PATCH v8 14/32] fanotify: Allow file handle encoding for unhashed events Gabriel Krisman Bertazi
2021-10-18 23:59 ` [PATCH v8 15/32] fanotify: Encode empty file handle when no inode is provided Gabriel Krisman Bertazi
2021-10-18 23:59 ` [PATCH v8 16/32] fanotify: Require fid_mode for any non-fd event Gabriel Krisman Bertazi
2021-10-19 0:00 ` [PATCH v8 17/32] fsnotify: Support FS_ERROR event type Gabriel Krisman Bertazi
2021-10-19 0:00 ` [PATCH v8 18/32] fanotify: Reserve UAPI bits for FAN_FS_ERROR Gabriel Krisman Bertazi
2021-10-19 0:00 ` [PATCH v8 19/32] fanotify: Pre-allocate pool of error events Gabriel Krisman Bertazi
2021-10-19 5:38 ` Amir Goldstein
2021-10-19 11:52 ` Jan Kara
2021-10-19 0:00 ` [PATCH v8 20/32] fanotify: Dynamically resize the FAN_FS_ERROR pool Gabriel Krisman Bertazi
2021-10-19 5:50 ` Amir Goldstein
2021-10-19 12:03 ` Jan Kara
2021-10-21 18:17 ` Gabriel Krisman Bertazi
2021-10-21 19:29 ` Jan Kara
2021-10-19 0:00 ` [PATCH v8 21/32] fanotify: Support enqueueing of error events Gabriel Krisman Bertazi
2021-10-19 5:52 ` Amir Goldstein
2021-10-19 0:00 ` [PATCH v8 22/32] fanotify: Support merging " Gabriel Krisman Bertazi
2021-10-19 5:56 ` Amir Goldstein
2021-10-19 13:52 ` Jan Kara
2021-10-19 0:00 ` [PATCH v8 23/32] fanotify: Wrap object_fh inline space in a creator macro Gabriel Krisman Bertazi
2021-10-19 6:09 ` Amir Goldstein
2021-10-19 13:58 ` Jan Kara
2021-10-19 0:00 ` [PATCH v8 24/32] fanotify: Add helpers to decide whether to report FID/DFID Gabriel Krisman Bertazi
2021-10-19 6:12 ` Amir Goldstein
2021-10-19 14:03 ` Jan Kara
2021-10-19 0:00 ` [PATCH v8 25/32] fanotify: Report fid entry even for zero-length file_handle Gabriel Krisman Bertazi
2021-10-19 6:13 ` Amir Goldstein
2021-10-19 14:08 ` Jan Kara
2021-10-19 0:00 ` [PATCH v8 26/32] fanotify: WARN_ON against too large file handles Gabriel Krisman Bertazi
2021-10-19 6:02 ` Amir Goldstein
2021-10-19 14:06 ` Jan Kara
2021-10-19 0:00 ` [PATCH v8 27/32] fanotify: Report fid info for file related file system errors Gabriel Krisman Bertazi
2021-10-19 6:07 ` Amir Goldstein
2021-10-19 14:41 ` Jan Kara
2021-10-19 0:00 ` [PATCH v8 28/32] fanotify: Emit generic error info for error event Gabriel Krisman Bertazi
2021-10-19 0:00 ` [PATCH v8 29/32] fanotify: Allow users to request FAN_FS_ERROR events Gabriel Krisman Bertazi
2021-10-19 5:57 ` Amir Goldstein
2021-10-19 15:24 ` Jan Kara
2021-10-19 0:00 ` [PATCH v8 30/32] ext4: Send notifications on error Gabriel Krisman Bertazi
2021-10-19 15:44 ` Jan Kara
2021-10-19 16:01 ` Jan Kara
2021-10-19 16:54 ` Gabriel Krisman Bertazi
2021-10-20 3:11 ` Theodore Ts'o
2021-10-19 0:00 ` [PATCH v8 31/32] samples: Add fs error monitoring example Gabriel Krisman Bertazi
2021-10-19 15:49 ` Jan Kara
2021-10-28 15:18 ` Guenter Roeck
2021-10-28 18:56 ` Gabriel Krisman Bertazi
2021-10-28 19:56 ` Guenter Roeck
2021-11-01 11:42 ` Jan Kara [this message]
2021-10-19 0:00 ` [PATCH v8 32/32] docs: Document the FAN_FS_ERROR event Gabriel Krisman Bertazi
2021-10-19 16:47 ` Jan Kara
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=20211101114222.GA21679@quack2.suse.cz \
--to=jack@suse.cz \
--cc=amir73il@gmail.com \
--cc=david@fromorbit.com \
--cc=dhowells@redhat.com \
--cc=djwong@kernel.org \
--cc=jack@suse.com \
--cc=kernel@collabora.com \
--cc=khazhy@google.com \
--cc=krisman@collabora.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=tytso@mit.edu \
/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).