From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 5F936C433F5 for ; Fri, 20 May 2022 18:09:52 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1349247AbiETSJv (ORCPT ); Fri, 20 May 2022 14:09:51 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:57608 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231983AbiETSJt (ORCPT ); Fri, 20 May 2022 14:09:49 -0400 Received: from bhuna.collabora.co.uk (bhuna.collabora.co.uk [46.235.227.227]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id CCD7B18C056 for ; Fri, 20 May 2022 11:09:47 -0700 (PDT) Received: from [127.0.0.1] (localhost [127.0.0.1]) (Authenticated sender: krisman) with ESMTPSA id B10D61F46723 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=collabora.com; s=mail; t=1653070185; bh=npGcKO8IeQGtHSG3g/Mw8ude52to8gtFr3hQPov40o4=; h=From:To:Cc:Subject:Date:From; b=DgKMCZdwP4LVQeGW94tFjGu7/lYBV/uPYe2u2ldQ+P+kQl759iIKKgiAe+ziWrzs4 VK+nna8hxjcZT9GMFTdVUtrYImfHtHQDbxlikTjgtzf0ypBPDtwsc9ATKtpdg8k2Y+ oTzgEjl9sXxyxdeQ0Dd2NHFgUNQQ0kNQCw+O3k+ghE07/SXWRsP2i5GZyJFUIxtXrW ewLb7hN5BSQ5zIU7PlL7paaEk9c0bbu3G9us3AS7GOKF/rDcO9KmDr7TLLgEAIlHq0 x68LHCjfXwACJRG7sNv2kzWzM9swPORHTHWYBbjXiyBRoyj3jZFSNVqyaOPE0h3Prj H0sbgUguBrZeA== From: Gabriel Krisman Bertazi To: all.manpages@gmail.com, mtk.manpages@gmail.com Cc: linux-man@vger.kernel.org, Gabriel Krisman Bertazi , Jan Kara , Amir Goldstein , Matthew Bobrowski Subject: [PATCH RESEND v5] fanotify.7, fanotify_mark.2: Document FAN_FS_ERROR Date: Fri, 20 May 2022 14:09:35 -0400 Message-Id: <20220520180935.37796-1-krisman@collabora.com> X-Mailer: git-send-email 2.36.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-man@vger.kernel.org FAN_FS_ERROR is a new event for fanotify to report filesystem errors that might lead to some corruption. This documents how to use the feature and specific caveats. Reviewed-by: Jan Kara Reviewed-by: Amir Goldstein Reviewed-by: Matthew Bobrowski Signed-off-by: Gabriel Krisman Bertazi --- as discussed this is rebased on top of the PIDFD documentation: commit 207080c7f7f5 ("fanotify: Document FAN_REPORT_PIDFD Feature") changes since v5: (matthew) - typo fix changes since v4: (Matthew) - Grammar fixes - Reword sections (Jan) - Explain fs error only apply to some errors (Amir) - Clarify what supported by ext4 means. Changes since v3: (Matthew) - Rewording and fixes from github) (amir) - 5.15 -> 5.16 Changes since v2: (matthew) - Grammar - List filesystems that support the feature - file system -> filesystem Changes since v1: (Matthew) - Grammar fixes - Don't use the term "submitted" for events sent to the listener - Clarify the kind of information that is file system specific --- man2/fanotify_mark.2 | 30 +++++++++++++++++++++ man7/fanotify.7 | 64 ++++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 94 insertions(+) diff --git a/man2/fanotify_mark.2 b/man2/fanotify_mark.2 index 9a45cbb77893..3dc538b7f84b 100644 --- a/man2/fanotify_mark.2 +++ b/man2/fanotify_mark.2 @@ -203,6 +203,29 @@ Create an event when a marked file or directory itself is deleted. An fanotify group that identifies filesystem objects by file handles is required. .TP +.BR FAN_FS_ERROR " (since Linux 5.16)" +.\" commit 9709bd548f11a092d124698118013f66e1740f9b +Create an event when a filesystem error +leading to inconsistent filesystem metadata is detected. +An additional information record of type +.B FAN_EVENT_INFO_TYPE_ERROR +is returned for each event in the read buffer. +An fanotify group that identifies filesystem objects by file handles +is required. +.IP +Events of such type are dependent on support +from the underlying filesystem. +At the time of writing, +only the +.B ext4 +filesystem reports +.B FAN_FS_ERROR +events. +.IP +See +.BR fanotify (7) +for additional details. +.TP .BR FAN_MOVED_FROM " (since Linux 5.1)" .\" commit 235328d1fa4251c6dcb32351219bb553a58838d2 Create an event when a file or directory has been moved from a marked @@ -391,6 +414,13 @@ and mask contains a flag for permission events or .BR FAN_ACCESS_PERM ). .TP +.B EINVAL +The group was initialized without +.B FAN_REPORT_FID +but one or more event types specified in the +.I mask +require it. +.TP .B ENODEV The filesystem object indicated by .I pathname diff --git a/man7/fanotify.7 b/man7/fanotify.7 index 57dd2b040380..3dc4113a551c 100644 --- a/man7/fanotify.7 +++ b/man7/fanotify.7 @@ -217,6 +217,25 @@ struct fanotify_event_info_pidfd { .EE .in .PP +In case of a +.B FAN_FS_ERROR +event, +an additional information record describing the error that occurred +is returned alongside the generic +.I fanotify_event_metadata +structure within the read buffer. +This structure is defined as follows: +.PP +.in +4n +.EX +struct fanotify_event_info_error { + struct fanotify_event_info_header hdr; + __s32 error; + __u32 error_count; +}; +.EE +.in +.PP All information records contain a nested structure of type .IR fanotify_event_info_header . This structure holds meta-information about the information record @@ -358,6 +377,9 @@ A child file or directory was deleted in a watched parent. .B FAN_DELETE_SELF A watched file or directory was deleted. .TP +.B FAN_FS_ERROR +A filesystem error was detected. +.TP .B FAN_MOVED_FROM A file or directory has been moved from a watched parent directory. .TP @@ -630,6 +652,25 @@ Once the event listener has dealt with an event and the pidfd is no longer required, the pidfd should be closed via .BR close(2) . .PP +The fields of the +.I fanotify_event_info_error +structure are as follows: +.TP +.I hdr +This is a structure of type +.IR fanotify_event_info_header . +The +.I info_type +field is set to +.BR FAN_EVENT_INFO_TYPE_ERROR . +.TP +.I error +Identifies the type of error that occurred. +.TP +.I error_count +This is a counter of the number of errors suppressed +since the last error was read. +.PP The following macros are provided to iterate over a buffer containing fanotify event metadata returned by a .BR read (2) @@ -719,6 +760,29 @@ field. In that case, the audit subsystem will log information about the access decision to the audit logs. .\" +.SS Monitoring filesystems for errors +A single FAN_FS_ERROR event is stored per filesystem at once. +Extra error messages are suppressed and accounted for +in the +.I error_count +field of the existing FAN_FS_ERROR event record, +but details about the errors are lost. +.PP +Errors reported by FAN_FS_ERROR are generic errno values +but not all kinds of error types are reported by all filesystems. +.PP +Errors not directly related to a file (i.e. super block corruption) +are reported with an invalid +.IR file_handle . +For these errors, the +.I file_handle +will have the field +.I handle_type +set to +.BR FILEID_INVALID , +and the handle buffer size set to +.BR 0 . +.\" .SS Closing the fanotify file descriptor When all file descriptors referring to the fanotify notification group are closed, the fanotify group is released and its resources -- 2.36.1