Commit d3f79db9 authored by Matthew Cassell's avatar Matthew Cassell Committed by Jonathan Corbet
Browse files

Documentation/trace: Fixed typos in the ftrace FLAGS section 



Fixed typos in the FTRACE_OPS_FL_RECURSION flag description.

Signed-off-by: default avatarMatthew Cassell <mcassell411@gmail.com>
Reviewed-by: default avatarRandy Dunlap <rdunlap@infradead.org>
Signed-off-by: default avatarJonathan Corbet <corbet@lwn.net>
Link: https://lore.kernel.org/r/20231223185845.2326-1-mcassell411@gmail.com
parent afa751e8

Documentation/trace/ftrace-uses.rst

+2 −2
Original line number Diff line number Diff line
@@ -182,7 +182,7 @@ FTRACE_OPS_FL_SAVE_REGS_IF_SUPPORTED 


FTRACE_OPS_FL_RECURSION

	By default, it is expected that the callback can handle recursion.

	But if the callback is not that worried about overehead, then

	But if the callback is not that worried about overhead, then

	setting this bit will add the recursion protection around the

	callback by calling a helper function that will do the recursion

	protection and only call the callback if it did not recurse.
@@ -190,7 +190,7 @@ FTRACE_OPS_FL_RECURSION 
	Note, if this flag is not set, and recursion does occur, it could

	cause the system to crash, and possibly reboot via a triple fault.



	Not, if this flag is set, then the callback will always be called

	Note, if this flag is set, then the callback will always be called

	with preemption disabled. If it is not set, then it is possible

	(but not guaranteed) that the callback will be called in

	preemptable context.