From 3490cd7c418cdb6e2a193366cf78659a688f3748 Mon Sep 17 00:00:00 2001 From: Amit Dhingra Date: Mon, 23 Oct 2023 20:31:57 +0200 Subject: [PATCH] Fixed Typo (#243) Close #242 --- lkmpg.tex | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lkmpg.tex b/lkmpg.tex index 778e0006..9675c4bd 100644 --- a/lkmpg.tex +++ b/lkmpg.tex @@ -1201,7 +1201,7 @@ \subsection{Manage /proc file with standard filesystem} The difference between file and inode operations is that file operations deal with the file itself whereas inode operations deal with ways of referencing the file, such as creating links to it. In \verb|/proc|, whenever we register a new file, we're allowed to specify which \cpp|struct inode_operations| will be used to access to it. -This is the mechanism we use, a \cpp|struct inode_operations| which includes a pointer to a \cpp|struct proc_ops| which includes pointers to our \cpp|procf_read| and \cpp|procfs_write| functions. +This is the mechanism we use, a \cpp|struct inode_operations| which includes a pointer to a \cpp|struct proc_ops| which includes pointers to our \cpp|procfs_read| and \cpp|procfs_write| functions. Another interesting point here is the \cpp|module_permission| function. This function is called whenever a process tries to do something with the \verb|/proc| file, and it can decide whether to allow access or not.