From: Gabriel Krisman Bertazi <krisman@collabora.com>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Jan Kara <jack@suse.com>, "Darrick J. Wong" <djwong@kernel.org>,
Theodore Tso <tytso@mit.edu>, David Howells <dhowells@redhat.com>,
Khazhismel Kumykov <khazhy@google.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Ext4 <linux-ext4@vger.kernel.org>,
Linux API <linux-api@vger.kernel.org>,
Matthew Bobrowski <repnop@google.com>,
kernel@collabora.com
Subject: Re: [PATCH v7 21/28] fanotify: Support merging of error events
Date: Mon, 18 Oct 2021 10:55:06 -0300 [thread overview]
Message-ID: <87ee8iphdx.fsf@collabora.com> (raw)
In-Reply-To: <CAOQ4uxizDrR=cnPQzSx8C7-b3fUCWujvpKeCrq0kcMK8kw3=mw@mail.gmail.com> (Amir Goldstein's message of "Fri, 15 Oct 2021 20:52:43 +0300")
Amir Goldstein <amir73il@gmail.com> writes:
> On Fri, Oct 15, 2021 at 7:54 PM Gabriel Krisman Bertazi
> <krisman@collabora.com> wrote:
>>
>> Amir Goldstein <amir73il@gmail.com> writes:
>>
>> > On Fri, Oct 15, 2021 at 12:39 AM Gabriel Krisman Bertazi
>> > <krisman@collabora.com> wrote:
>> >>
>> >> Error events (FAN_FS_ERROR) against the same file system can be merged
>> >> by simply iterating the error count. The hash is taken from the fsid,
>> >> without considering the FH. This means that only the first error object
>> >> is reported.
>> >>
>> >> Signed-off-by: Gabriel Krisman Bertazi <krisman@collabora.com>
>> >> ---
>> >> fs/notify/fanotify/fanotify.c | 39 ++++++++++++++++++++++++++++++++---
>> >> fs/notify/fanotify/fanotify.h | 4 +++-
>> >> 2 files changed, 39 insertions(+), 4 deletions(-)
>> >>
>> >> diff --git a/fs/notify/fanotify/fanotify.c b/fs/notify/fanotify/fanotify.c
>> >> index 9b970359570a..7032083df62a 100644
>> >> --- a/fs/notify/fanotify/fanotify.c
>> >> +++ b/fs/notify/fanotify/fanotify.c
>> >> @@ -111,6 +111,16 @@ static bool fanotify_name_event_equal(struct fanotify_name_event *fne1,
>> >> return fanotify_info_equal(info1, info2);
>> >> }
>> >>
>> >> +static bool fanotify_error_event_equal(struct fanotify_error_event *fee1,
>> >> + struct fanotify_error_event *fee2)
>> >> +{
>> >> + /* Error events against the same file system are always merged. */
>> >> + if (!fanotify_fsid_equal(&fee1->fsid, &fee2->fsid))
>> >> + return false;
>> >> +
>> >> + return true;
>> >> +}
>> >> +
>> >> static bool fanotify_should_merge(struct fanotify_event *old,
>> >> struct fanotify_event *new)
>> >> {
>> >> @@ -141,6 +151,9 @@ static bool fanotify_should_merge(struct fanotify_event *old,
>> >> case FANOTIFY_EVENT_TYPE_FID_NAME:
>> >> return fanotify_name_event_equal(FANOTIFY_NE(old),
>> >> FANOTIFY_NE(new));
>> >> + case FANOTIFY_EVENT_TYPE_FS_ERROR:
>> >> + return fanotify_error_event_equal(FANOTIFY_EE(old),
>> >> + FANOTIFY_EE(new));
>> >> default:
>> >> WARN_ON_ONCE(1);
>> >> }
>> >> @@ -148,6 +161,22 @@ static bool fanotify_should_merge(struct fanotify_event *old,
>> >> return false;
>> >> }
>> >>
>> >> +static void fanotify_merge_error_event(struct fanotify_error_event *dest,
>> >> + struct fanotify_error_event *origin)
>> >> +{
>> >> + dest->err_count++;
>> >> +}
>> >> +
>> >> +static void fanotify_merge_event(struct fanotify_event *dest,
>> >> + struct fanotify_event *origin)
>> >> +{
>> >> + dest->mask |= origin->mask;
>> >> +
>> >> + if (origin->type == FANOTIFY_EVENT_TYPE_FS_ERROR)
>> >> + fanotify_merge_error_event(FANOTIFY_EE(dest),
>> >> + FANOTIFY_EE(origin));
>> >> +}
>> >> +
>> >> /* Limit event merges to limit CPU overhead per event */
>> >> #define FANOTIFY_MAX_MERGE_EVENTS 128
>> >>
>> >> @@ -175,7 +204,7 @@ static int fanotify_merge(struct fsnotify_group *group,
>> >> if (++i > FANOTIFY_MAX_MERGE_EVENTS)
>> >> break;
>> >> if (fanotify_should_merge(old, new)) {
>> >> - old->mask |= new->mask;
>> >> + fanotify_merge_event(old, new);
>> >> return 1;
>> >> }
>> >> }
>> >> @@ -577,7 +606,8 @@ static struct fanotify_event *fanotify_alloc_name_event(struct inode *id,
>> >> static struct fanotify_event *fanotify_alloc_error_event(
>> >> struct fsnotify_group *group,
>> >> __kernel_fsid_t *fsid,
>> >> - const void *data, int data_type)
>> >> + const void *data, int data_type,
>> >> + unsigned int *hash)
>> >> {
>> >> struct fs_error_report *report =
>> >> fsnotify_data_error_report(data, data_type);
>> >> @@ -591,6 +621,9 @@ static struct fanotify_event *fanotify_alloc_error_event(
>> >> return NULL;
>> >>
>> >> fee->fae.type = FANOTIFY_EVENT_TYPE_FS_ERROR;
>> >> + fee->err_count = 1;
>> >> +
>> >> + *hash ^= fanotify_hash_fsid(fsid);
>> >>
>> >> return &fee->fae;
>> >> }
>> >
>> > Forgot to store fee->fsid?
>>
>> Not really. this is part of the FID info record support, which is done
>> in patch 23.
>>
>
> Sure, it does not really matter for bisection when FS_ERROR is not yet
> wired, but it is weird to compare event fsid's when they have not been
> initialized.
>
> Logically, storing the fsid in this patch would be better.
Makes sense. Will do!
Thanks,
--
Gabriel Krisman Bertazi
next prev parent reply other threads:[~2021-10-18 14:15 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-14 21:36 [PATCH v7 00/28] file system-wide error monitoring Gabriel Krisman Bertazi
2021-10-14 21:36 ` [PATCH v7 01/28] fsnotify: pass data_type to fsnotify_name() Gabriel Krisman Bertazi
2021-10-15 9:18 ` Jan Kara
2021-10-14 21:36 ` [PATCH v7 02/28] fsnotify: pass dentry instead of inode data Gabriel Krisman Bertazi
2021-10-15 13:39 ` Jan Kara
2021-10-18 9:11 ` Jan Kara
2021-10-14 21:36 ` [PATCH v7 03/28] fsnotify: clarify contract for create event hooks Gabriel Krisman Bertazi
2021-10-15 9:21 ` Jan Kara
2021-10-14 21:36 ` [PATCH v7 04/28] fsnotify: Don't insert unmergeable events in hashtable Gabriel Krisman Bertazi
2021-10-14 21:36 ` [PATCH v7 05/28] fanotify: Fold event size calculation to its own function Gabriel Krisman Bertazi
2021-10-14 21:36 ` [PATCH v7 06/28] fanotify: Split fsid check from other fid mode checks Gabriel Krisman Bertazi
2021-10-14 21:36 ` [PATCH v7 07/28] inotify: Don't force FS_IN_IGNORED Gabriel Krisman Bertazi
2021-10-14 21:36 ` [PATCH v7 08/28] fsnotify: Add helper to detect overflow_event Gabriel Krisman Bertazi
2021-10-14 21:36 ` [PATCH v7 09/28] fsnotify: Add wrapper around fsnotify_add_event Gabriel Krisman Bertazi
2021-10-14 21:36 ` [PATCH v7 10/28] fsnotify: Retrieve super block from the data field Gabriel Krisman Bertazi
2021-10-15 5:39 ` Amir Goldstein
2021-10-15 9:26 ` Jan Kara
2021-10-14 21:36 ` [PATCH v7 11/28] fsnotify: Pass group argument to free_event Gabriel Krisman Bertazi
2021-10-15 5:40 ` Amir Goldstein
2021-10-15 9:26 ` Jan Kara
2021-10-14 21:36 ` [PATCH v7 12/28] fanotify: Support null inode event in fanotify_dfid_inode Gabriel Krisman Bertazi
2021-10-15 5:49 ` Amir Goldstein
2021-10-15 9:30 ` Jan Kara
2021-10-14 21:36 ` [PATCH v7 13/28] fanotify: Allow file handle encoding for unhashed events Gabriel Krisman Bertazi
2021-10-14 21:36 ` [PATCH v7 14/28] fanotify: Encode empty file handle when no inode is provided Gabriel Krisman Bertazi
2021-10-15 6:02 ` Amir Goldstein
2021-10-15 9:32 ` Jan Kara
2021-10-14 21:36 ` [PATCH v7 15/28] fanotify: Require fid_mode for any non-fd event Gabriel Krisman Bertazi
2021-10-14 21:36 ` [PATCH v7 16/28] fsnotify: Support FS_ERROR event type Gabriel Krisman Bertazi
2021-10-14 21:36 ` [PATCH v7 17/28] fanotify: Reserve UAPI bits for FAN_FS_ERROR Gabriel Krisman Bertazi
2021-10-15 9:37 ` Jan Kara
2021-10-14 21:36 ` [PATCH v7 18/28] fanotify: Pre-allocate pool of error events Gabriel Krisman Bertazi
2021-10-15 6:19 ` Amir Goldstein
2021-10-15 7:33 ` Amir Goldstein
2021-10-15 9:46 ` Jan Kara
2021-10-14 21:36 ` [PATCH v7 19/28] fanotify: Limit number of marks with FAN_FS_ERROR per group Gabriel Krisman Bertazi
2021-10-15 6:15 ` Amir Goldstein
2021-10-15 16:53 ` Gabriel Krisman Bertazi
2021-10-15 17:49 ` Amir Goldstein
2021-10-14 21:36 ` [PATCH v7 20/28] fanotify: Support enqueueing of error events Gabriel Krisman Bertazi
2021-10-15 7:04 ` Amir Goldstein
2021-10-15 16:50 ` Gabriel Krisman Bertazi
2021-10-15 12:34 ` Jan Kara
2021-10-14 21:36 ` [PATCH v7 21/28] fanotify: Support merging " Gabriel Krisman Bertazi
2021-10-15 7:09 ` Amir Goldstein
2021-10-15 16:54 ` Gabriel Krisman Bertazi
2021-10-15 17:52 ` Amir Goldstein
2021-10-18 13:55 ` Gabriel Krisman Bertazi [this message]
2021-10-15 12:43 ` Jan Kara
2021-10-14 21:36 ` [PATCH v7 22/28] fanotify: Report FID entry even for zero-length file_handle Gabriel Krisman Bertazi
2021-10-15 8:10 ` Amir Goldstein
2021-10-15 13:13 ` Jan Kara
2021-10-14 21:36 ` [PATCH v7 23/28] fanotify: Report fid info for file related file system errors Gabriel Krisman Bertazi
2021-10-15 7:56 ` Amir Goldstein
2021-10-15 13:38 ` Jan Kara
2021-10-14 21:36 ` [PATCH v7 24/28] fanotify: Emit generic error info for error event Gabriel Krisman Bertazi
2021-10-15 8:13 ` Amir Goldstein
2021-10-15 12:47 ` Jan Kara
2021-10-14 21:36 ` [PATCH v7 25/28] fanotify: Allow users to request FAN_FS_ERROR events Gabriel Krisman Bertazi
2021-10-15 8:27 ` Amir Goldstein
2021-10-15 12:49 ` Jan Kara
2021-10-14 21:36 ` [PATCH v7 26/28] ext4: Send notifications on error Gabriel Krisman Bertazi
2021-10-14 21:59 ` Theodore Ts'o
2021-10-14 21:36 ` [PATCH v7 27/28] samples: Add fs error monitoring example Gabriel Krisman Bertazi
2021-10-14 21:36 ` [PATCH v7 28/28] docs: Document the FAN_FS_ERROR event Gabriel Krisman Bertazi
2021-10-15 8:38 ` [PATCH v7 00/28] file system-wide error monitoring Amir Goldstein
2021-10-15 9:16 ` 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=87ee8iphdx.fsf@collabora.com \
--to=krisman@collabora.com \
--cc=amir73il@gmail.com \
--cc=dhowells@redhat.com \
--cc=djwong@kernel.org \
--cc=jack@suse.com \
--cc=kernel@collabora.com \
--cc=khazhy@google.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=repnop@google.com \
--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).