Skip to content

Commit d3f79db

Browse files
Matthew CassellJonathan Corbet
authored andcommitted
Documentation/trace: Fixed typos in the ftrace FLAGS section
Fixed typos in the FTRACE_OPS_FL_RECURSION flag description. Signed-off-by: Matthew Cassell <mcassell411@gmail.com> Reviewed-by: Randy Dunlap <rdunlap@infradead.org> Signed-off-by: Jonathan Corbet <corbet@lwn.net> Link: https://lore.kernel.org/r/20231223185845.2326-1-mcassell411@gmail.com
1 parent afa751e commit d3f79db

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

Documentation/trace/ftrace-uses.rst

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -182,15 +182,15 @@ FTRACE_OPS_FL_SAVE_REGS_IF_SUPPORTED
182182

183183
FTRACE_OPS_FL_RECURSION
184184
By default, it is expected that the callback can handle recursion.
185-
But if the callback is not that worried about overehead, then
185+
But if the callback is not that worried about overhead, then
186186
setting this bit will add the recursion protection around the
187187
callback by calling a helper function that will do the recursion
188188
protection and only call the callback if it did not recurse.
189189

190190
Note, if this flag is not set, and recursion does occur, it could
191191
cause the system to crash, and possibly reboot via a triple fault.
192192

193-
Not, if this flag is set, then the callback will always be called
193+
Note, if this flag is set, then the callback will always be called
194194
with preemption disabled. If it is not set, then it is possible
195195
(but not guaranteed) that the callback will be called in
196196
preemptable context.

0 commit comments

Comments
 (0)