kevin/linux
1
Fork 0
Code

Documentation: tracing: Fix spelling mistakes

Browse Source 
Fix spelling mistakes in the documentation.

Signed-off-by: Saurav Shah <sauravshah.31@gmail.com>
Link: https://lore.kernel.org/r/20240501233659.25441-1-sauravshah.31@gmail.com
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
This commit is contained in:
Saurav Shah 2024-05-02 05:06:59 +05:30 committed by Jonathan Corbet
parent 55b8d0a332
commit dd29dfe78b
3 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
Documentation/trace/fprobetrace.rst
View File

@ -74,7 +74,7 @@ Function arguments at exit
-------------------------- --------------------------
Function arguments can be accessed at exit probe using $arg<N> fetcharg. This Function arguments can be accessed at exit probe using $arg<N> fetcharg. This
is useful to record the function parameter and return value at once, and is useful to record the function parameter and return value at once, and
trace the difference of structure fields (for debuging a function whether it trace the difference of structure fields (for debugging a function whether it
correctly updates the given data structure or not) correctly updates the given data structure or not)
See the :ref:`sample<fprobetrace_exit_args_sample>` below for how it works. See the :ref:`sample<fprobetrace_exit_args_sample>` below for how it works.
@ -248,4 +248,4 @@ mode. You can trace that changes with return probe.
cat-143 [007] ...1. 1945.720616: vfs_open__entry: (vfs_open+0x4/0x40) mode=0x1 inode=0x0 cat-143 [007] ...1. 1945.720616: vfs_open__entry: (vfs_open+0x4/0x40) mode=0x1 inode=0x0
cat-143 [007] ...1. 1945.728263: vfs_open__exit: (do_open+0x274/0x3d0 <- vfs_open) mode=0xa800d inode=0xffff888004ada8d8 cat-143 [007] ...1. 1945.728263: vfs_open__exit: (do_open+0x274/0x3d0 <- vfs_open) mode=0xa800d inode=0xffff888004ada8d8
You can see the `file::f_mode` and `file::f_inode` are upated in `vfs_open()`. You can see the `file::f_mode` and `file::f_inode` are updated in `vfs_open()`.

2
Documentation/trace/ftrace.rst
View File

@ -1968,7 +1968,7 @@ wakeup
One common case that people are interested in tracing is the One common case that people are interested in tracing is the
time it takes for a task that is woken to actually wake up. time it takes for a task that is woken to actually wake up.
Now for non Real-Time tasks, this can be arbitrary. But tracing Now for non Real-Time tasks, this can be arbitrary. But tracing
it none the less can be interesting. it nonetheless can be interesting.
Without function tracing:: Without function tracing::

2
Documentation/trace/kprobetrace.rst
View File

@ -74,7 +74,7 @@ Function arguments at kretprobe
------------------------------- -------------------------------
Function arguments can be accessed at kretprobe using $arg<N> fetcharg. This Function arguments can be accessed at kretprobe using $arg<N> fetcharg. This
is useful to record the function parameter and return value at once, and is useful to record the function parameter and return value at once, and
trace the difference of structure fields (for debuging a function whether it trace the difference of structure fields (for debugging a function whether it
correctly updates the given data structure or not). correctly updates the given data structure or not).
See the :ref:`sample<fprobetrace_exit_args_sample>` in fprobe event for how See the :ref:`sample<fprobetrace_exit_args_sample>` in fprobe event for how
it works. it works.