On Tue, Jun 29, 2021 at 10:13 PM Gabriel Krisman Bertazi <krisman@xxxxxxxxxxxxx> wrote: > > Document the FAN_FS_ERROR event for user administrators and user space > developers. > > Signed-off-by: Gabriel Krisman Bertazi <krisman@xxxxxxxxxxxxx> > > --- > Changes since v1: > - Drop references to location record > - Explain that the inode field is optional > - Explain we are reporting only the first error > --- > .../admin-guide/filesystem-monitoring.rst | 70 +++++++++++++++++++ > Documentation/admin-guide/index.rst | 1 + > 2 files changed, 71 insertions(+) > create mode 100644 Documentation/admin-guide/filesystem-monitoring.rst > > diff --git a/Documentation/admin-guide/filesystem-monitoring.rst b/Documentation/admin-guide/filesystem-monitoring.rst > new file mode 100644 > index 000000000000..c0ab1ad268b8 > --- /dev/null > +++ b/Documentation/admin-guide/filesystem-monitoring.rst > @@ -0,0 +1,70 @@ > +.. SPDX-License-Identifier: GPL-2.0 > + > +==================================== > +File system Monitoring with fanotify > +==================================== It is great that you are adding an admin-guide book and it is surely not your fault that there is no existing admin-guide for fanotify to add to. However, the name of the book as well as this title are more generic than what you describe. You see, watching all the deleted files in a filesystem or all modified files in a mount may also be considered as "filesystem monitoring" by some. So my only request is that you keep the book name and title as is, but place your content under a chapter about "filesystem error monitoring". This way, other people can later fill the gaps. (CC Matthew Borowski who indicated his interest in doing so) Thanks, Amir.
