From 9db8c92cf50379fed8e2f26a259bc9793e7fbe67 Mon Sep 17 00:00:00 2001 From: linD026 Date: Thu, 8 Sep 2022 08:24:47 +0800 Subject: [PATCH] Improve the description of proc in file-ops Currently, the description of the proc_ops in the file operation section will confuse the reader with registering the device. Add more hints to avoid it. --- lkmpg.tex | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/lkmpg.tex b/lkmpg.tex index 5f7b9a1..530ca74 100644 --- a/lkmpg.tex +++ b/lkmpg.tex @@ -954,7 +954,8 @@ An instance of \cpp|struct file_operations| containing pointers to functions tha Since Linux v3.14, the read, write and seek operations are guaranteed for thread-safe by using the \cpp|f_pos| specific lock, which makes the file position update to become the mutual exclusion. So, we can safely implement those operations without unnecessary locking. -Since Linux v5.6, the \cpp|proc_ops| structure was introduced to replace the use of the \cpp|file_operations| structure when registering proc handlers. +Additionally, since Linux v5.6, the \cpp|proc_ops| structure was introduced to replace the use of the \cpp|file_operations| structure when registering proc handlers. +See more information in the \ref{sec:proc_ops} section. \subsection{The file structure} \label{sec:file_struct}