1 ================================= 1 =================================
2 Using ftrace to hook to functions 2 Using ftrace to hook to functions
3 ================================= 3 =================================
4 4
5 .. Copyright 2017 VMware Inc. 5 .. Copyright 2017 VMware Inc.
6 .. Author: Steven Rostedt <srostedt@goodmis 6 .. Author: Steven Rostedt <srostedt@goodmis.org>
7 .. License: The GNU Free Documentation Lice 7 .. License: The GNU Free Documentation License, Version 1.2
8 .. (dual licensed under the GPL 8 .. (dual licensed under the GPL v2)
9 9
10 Written for: 4.14 10 Written for: 4.14
11 11
12 Introduction 12 Introduction
13 ============ 13 ============
14 14
15 The ftrace infrastructure was originally creat 15 The ftrace infrastructure was originally created to attach callbacks to the
16 beginning of functions in order to record and 16 beginning of functions in order to record and trace the flow of the kernel.
17 But callbacks to the start of a function can h 17 But callbacks to the start of a function can have other use cases. Either
18 for live kernel patching, or for security moni 18 for live kernel patching, or for security monitoring. This document describes
19 how to use ftrace to implement your own functi 19 how to use ftrace to implement your own function callbacks.
20 20
21 21
22 The ftrace context 22 The ftrace context
23 ================== 23 ==================
24 .. warning:: 24 .. warning::
25 25
26 The ability to add a callback to almost any 26 The ability to add a callback to almost any function within the
27 kernel comes with risks. A callback can be c 27 kernel comes with risks. A callback can be called from any context
28 (normal, softirq, irq, and NMI). Callbacks c 28 (normal, softirq, irq, and NMI). Callbacks can also be called just before
29 going to idle, during CPU bring up and taked 29 going to idle, during CPU bring up and takedown, or going to user space.
30 This requires extra care to what can be done 30 This requires extra care to what can be done inside a callback. A callback
31 can be called outside the protective scope o 31 can be called outside the protective scope of RCU.
32 32
33 There are helper functions to help against rec 33 There are helper functions to help against recursion, and making sure
34 RCU is watching. These are explained below. 34 RCU is watching. These are explained below.
35 35
36 36
37 The ftrace_ops structure 37 The ftrace_ops structure
38 ======================== 38 ========================
39 39
40 To register a function callback, a ftrace_ops 40 To register a function callback, a ftrace_ops is required. This structure
41 is used to tell ftrace what function should be 41 is used to tell ftrace what function should be called as the callback
42 as well as what protections the callback will 42 as well as what protections the callback will perform and not require
43 ftrace to handle. 43 ftrace to handle.
44 44
45 There is only one field that is needed to be s 45 There is only one field that is needed to be set when registering
46 an ftrace_ops with ftrace: 46 an ftrace_ops with ftrace:
47 47
48 .. code-block:: c 48 .. code-block:: c
49 49
50 struct ftrace_ops ops = { 50 struct ftrace_ops ops = {
51 .func = my_callback_ 51 .func = my_callback_func,
52 .flags = MY_FTRACE_FL 52 .flags = MY_FTRACE_FLAGS
53 .private = any_private_ 53 .private = any_private_data_structure,
54 }; 54 };
55 55
56 Both .flags and .private are optional. Only .f 56 Both .flags and .private are optional. Only .func is required.
57 57
58 To enable tracing call:: 58 To enable tracing call::
59 59
60 register_ftrace_function(&ops); 60 register_ftrace_function(&ops);
61 61
62 To disable tracing call:: 62 To disable tracing call::
63 63
64 unregister_ftrace_function(&ops); 64 unregister_ftrace_function(&ops);
65 65
66 The above is defined by including the header:: 66 The above is defined by including the header::
67 67
68 #include <linux/ftrace.h> 68 #include <linux/ftrace.h>
69 69
70 The registered callback will start being calle 70 The registered callback will start being called some time after the
71 register_ftrace_function() is called and befor 71 register_ftrace_function() is called and before it returns. The exact time
72 that callbacks start being called is dependent 72 that callbacks start being called is dependent upon architecture and scheduling
73 of services. The callback itself will have to 73 of services. The callback itself will have to handle any synchronization if it
74 must begin at an exact moment. 74 must begin at an exact moment.
75 75
76 The unregister_ftrace_function() will guarante 76 The unregister_ftrace_function() will guarantee that the callback is
77 no longer being called by functions after the 77 no longer being called by functions after the unregister_ftrace_function()
78 returns. Note that to perform this guarantee, 78 returns. Note that to perform this guarantee, the unregister_ftrace_function()
79 may take some time to finish. 79 may take some time to finish.
80 80
81 81
82 The callback function 82 The callback function
83 ===================== 83 =====================
84 84
85 The prototype of the callback function is as f 85 The prototype of the callback function is as follows (as of v4.14):
86 86
87 .. code-block:: c 87 .. code-block:: c
88 88
89 void callback_func(unsigned long ip, unsign 89 void callback_func(unsigned long ip, unsigned long parent_ip,
90 struct ftrace_ops *op, s 90 struct ftrace_ops *op, struct pt_regs *regs);
91 91
92 @ip 92 @ip
93 This is the instruction pointer of th 93 This is the instruction pointer of the function that is being traced.
94 (where the fentry or mcount is within 94 (where the fentry or mcount is within the function)
95 95
96 @parent_ip 96 @parent_ip
97 This is the instruction pointer of the 97 This is the instruction pointer of the function that called the
98 the function being traced (where the c 98 the function being traced (where the call of the function occurred).
99 99
100 @op 100 @op
101 This is a pointer to ftrace_ops that w 101 This is a pointer to ftrace_ops that was used to register the callback.
102 This can be used to pass data to the c 102 This can be used to pass data to the callback via the private pointer.
103 103
104 @regs 104 @regs
105 If the FTRACE_OPS_FL_SAVE_REGS or FTRA 105 If the FTRACE_OPS_FL_SAVE_REGS or FTRACE_OPS_FL_SAVE_REGS_IF_SUPPORTED
106 flags are set in the ftrace_ops struct 106 flags are set in the ftrace_ops structure, then this will be pointing
107 to the pt_regs structure like it would 107 to the pt_regs structure like it would be if an breakpoint was placed
108 at the start of the function where ftr 108 at the start of the function where ftrace was tracing. Otherwise it
109 either contains garbage, or NULL. 109 either contains garbage, or NULL.
110 110
111 Protect your callback 111 Protect your callback
112 ===================== 112 =====================
113 113
114 As functions can be called from anywhere, and 114 As functions can be called from anywhere, and it is possible that a function
115 called by a callback may also be traced, and c 115 called by a callback may also be traced, and call that same callback,
116 recursion protection must be used. There are t 116 recursion protection must be used. There are two helper functions that
117 can help in this regard. If you start your cod 117 can help in this regard. If you start your code with:
118 118
119 .. code-block:: c 119 .. code-block:: c
120 120
121 int bit; 121 int bit;
122 122
123 bit = ftrace_test_recursion_trylock(ip 123 bit = ftrace_test_recursion_trylock(ip, parent_ip);
124 if (bit < 0) 124 if (bit < 0)
125 return; 125 return;
126 126
127 and end it with: 127 and end it with:
128 128
129 .. code-block:: c 129 .. code-block:: c
130 130
131 ftrace_test_recursion_unlock(bit); 131 ftrace_test_recursion_unlock(bit);
132 132
133 The code in between will be safe to use, even 133 The code in between will be safe to use, even if it ends up calling a
134 function that the callback is tracing. Note, o 134 function that the callback is tracing. Note, on success,
135 ftrace_test_recursion_trylock() will disable p 135 ftrace_test_recursion_trylock() will disable preemption, and the
136 ftrace_test_recursion_unlock() will enable it 136 ftrace_test_recursion_unlock() will enable it again (if it was previously
137 enabled). The instruction pointer (ip) and its 137 enabled). The instruction pointer (ip) and its parent (parent_ip) is passed to
138 ftrace_test_recursion_trylock() to record wher 138 ftrace_test_recursion_trylock() to record where the recursion happened
139 (if CONFIG_FTRACE_RECORD_RECURSION is set). 139 (if CONFIG_FTRACE_RECORD_RECURSION is set).
140 140
141 Alternatively, if the FTRACE_OPS_FL_RECURSION 141 Alternatively, if the FTRACE_OPS_FL_RECURSION flag is set on the ftrace_ops
142 (as explained below), then a helper trampoline 142 (as explained below), then a helper trampoline will be used to test
143 for recursion for the callback and no recursio 143 for recursion for the callback and no recursion test needs to be done.
144 But this is at the expense of a slightly more 144 But this is at the expense of a slightly more overhead from an extra
145 function call. 145 function call.
146 146
147 If your callback accesses any data or critical 147 If your callback accesses any data or critical section that requires RCU
148 protection, it is best to make sure that RCU i 148 protection, it is best to make sure that RCU is "watching", otherwise
149 that data or critical section will not be prot 149 that data or critical section will not be protected as expected. In this
150 case add: 150 case add:
151 151
152 .. code-block:: c 152 .. code-block:: c
153 153
154 if (!rcu_is_watching()) 154 if (!rcu_is_watching())
155 return; 155 return;
156 156
157 Alternatively, if the FTRACE_OPS_FL_RCU flag i 157 Alternatively, if the FTRACE_OPS_FL_RCU flag is set on the ftrace_ops
158 (as explained below), then a helper trampoline 158 (as explained below), then a helper trampoline will be used to test
159 for rcu_is_watching for the callback and no ot 159 for rcu_is_watching for the callback and no other test needs to be done.
160 But this is at the expense of a slightly more 160 But this is at the expense of a slightly more overhead from an extra
161 function call. 161 function call.
162 162
163 163
164 The ftrace FLAGS 164 The ftrace FLAGS
165 ================ 165 ================
166 166
167 The ftrace_ops flags are all defined and docum 167 The ftrace_ops flags are all defined and documented in include/linux/ftrace.h.
168 Some of the flags are used for internal infras 168 Some of the flags are used for internal infrastructure of ftrace, but the
169 ones that users should be aware of are the fol 169 ones that users should be aware of are the following:
170 170
171 FTRACE_OPS_FL_SAVE_REGS 171 FTRACE_OPS_FL_SAVE_REGS
172 If the callback requires reading or mo 172 If the callback requires reading or modifying the pt_regs
173 passed to the callback, then it must s 173 passed to the callback, then it must set this flag. Registering
174 a ftrace_ops with this flag set on an 174 a ftrace_ops with this flag set on an architecture that does not
175 support passing of pt_regs to the call 175 support passing of pt_regs to the callback will fail.
176 176
177 FTRACE_OPS_FL_SAVE_REGS_IF_SUPPORTED 177 FTRACE_OPS_FL_SAVE_REGS_IF_SUPPORTED
178 Similar to SAVE_REGS but the registeri 178 Similar to SAVE_REGS but the registering of a
179 ftrace_ops on an architecture that doe 179 ftrace_ops on an architecture that does not support passing of regs
180 will not fail with this flag set. But 180 will not fail with this flag set. But the callback must check if
181 regs is NULL or not to determine if th 181 regs is NULL or not to determine if the architecture supports it.
182 182
183 FTRACE_OPS_FL_RECURSION 183 FTRACE_OPS_FL_RECURSION
184 By default, it is expected that the ca 184 By default, it is expected that the callback can handle recursion.
185 But if the callback is not that worrie !! 185 But if the callback is not that worried about overehead, then
186 setting this bit will add the recursio 186 setting this bit will add the recursion protection around the
187 callback by calling a helper function 187 callback by calling a helper function that will do the recursion
188 protection and only call the callback 188 protection and only call the callback if it did not recurse.
189 189
190 Note, if this flag is not set, and rec 190 Note, if this flag is not set, and recursion does occur, it could
191 cause the system to crash, and possibl 191 cause the system to crash, and possibly reboot via a triple fault.
192 192
193 Note, if this flag is set, then the ca !! 193 Not, if this flag is set, then the callback will always be called
194 with preemption disabled. If it is not 194 with preemption disabled. If it is not set, then it is possible
195 (but not guaranteed) that the callback 195 (but not guaranteed) that the callback will be called in
196 preemptable context. 196 preemptable context.
197 197
198 FTRACE_OPS_FL_IPMODIFY 198 FTRACE_OPS_FL_IPMODIFY
199 Requires FTRACE_OPS_FL_SAVE_REGS set. 199 Requires FTRACE_OPS_FL_SAVE_REGS set. If the callback is to "hijack"
200 the traced function (have another func 200 the traced function (have another function called instead of the
201 traced function), it requires setting 201 traced function), it requires setting this flag. This is what live
202 kernel patches uses. Without this flag 202 kernel patches uses. Without this flag the pt_regs->ip can not be
203 modified. 203 modified.
204 204
205 Note, only one ftrace_ops with FTRACE_ 205 Note, only one ftrace_ops with FTRACE_OPS_FL_IPMODIFY set may be
206 registered to any given function at a 206 registered to any given function at a time.
207 207
208 FTRACE_OPS_FL_RCU 208 FTRACE_OPS_FL_RCU
209 If this is set, then the callback will 209 If this is set, then the callback will only be called by functions
210 where RCU is "watching". This is requi 210 where RCU is "watching". This is required if the callback function
211 performs any rcu_read_lock() operation 211 performs any rcu_read_lock() operation.
212 212
213 RCU stops watching when the system goe 213 RCU stops watching when the system goes idle, the time when a CPU
214 is taken down and comes back online, a 214 is taken down and comes back online, and when entering from kernel
215 to user space and back to kernel space 215 to user space and back to kernel space. During these transitions,
216 a callback may be executed and RCU syn 216 a callback may be executed and RCU synchronization will not protect
217 it. 217 it.
218 218
219 FTRACE_OPS_FL_PERMANENT 219 FTRACE_OPS_FL_PERMANENT
220 If this is set on any ftrace ops, then 220 If this is set on any ftrace ops, then the tracing cannot disabled by
221 writing 0 to the proc sysctl ftrace_en 221 writing 0 to the proc sysctl ftrace_enabled. Equally, a callback with
222 the flag set cannot be registered if f 222 the flag set cannot be registered if ftrace_enabled is 0.
223 223
224 Livepatch uses it not to lose the func 224 Livepatch uses it not to lose the function redirection, so the system
225 stays protected. 225 stays protected.
226 226
227 227
228 Filtering which functions to trace 228 Filtering which functions to trace
229 ================================== 229 ==================================
230 230
231 If a callback is only to be called from specif 231 If a callback is only to be called from specific functions, a filter must be
232 set up. The filters are added by name, or ip i 232 set up. The filters are added by name, or ip if it is known.
233 233
234 .. code-block:: c 234 .. code-block:: c
235 235
236 int ftrace_set_filter(struct ftrace_ops *op 236 int ftrace_set_filter(struct ftrace_ops *ops, unsigned char *buf,
237 int len, int reset); 237 int len, int reset);
238 238
239 @ops 239 @ops
240 The ops to set the filter with 240 The ops to set the filter with
241 241
242 @buf 242 @buf
243 The string that holds the function fil 243 The string that holds the function filter text.
244 @len 244 @len
245 The length of the string. 245 The length of the string.
246 246
247 @reset 247 @reset
248 Non-zero to reset all filters before a 248 Non-zero to reset all filters before applying this filter.
249 249
250 Filters denote which functions should be enabl 250 Filters denote which functions should be enabled when tracing is enabled.
251 If @buf is NULL and reset is set, all function 251 If @buf is NULL and reset is set, all functions will be enabled for tracing.
252 252
253 The @buf can also be a glob expression to enab 253 The @buf can also be a glob expression to enable all functions that
254 match a specific pattern. 254 match a specific pattern.
255 255
256 See Filter Commands in :file:`Documentation/tr 256 See Filter Commands in :file:`Documentation/trace/ftrace.rst`.
257 257
258 To just trace the schedule function: 258 To just trace the schedule function:
259 259
260 .. code-block:: c 260 .. code-block:: c
261 261
262 ret = ftrace_set_filter(&ops, "schedule", s 262 ret = ftrace_set_filter(&ops, "schedule", strlen("schedule"), 0);
263 263
264 To add more functions, call the ftrace_set_fil 264 To add more functions, call the ftrace_set_filter() more than once with the
265 @reset parameter set to zero. To remove the cu 265 @reset parameter set to zero. To remove the current filter set and replace it
266 with new functions defined by @buf, have @rese 266 with new functions defined by @buf, have @reset be non-zero.
267 267
268 To remove all the filtered functions and trace 268 To remove all the filtered functions and trace all functions:
269 269
270 .. code-block:: c 270 .. code-block:: c
271 271
272 ret = ftrace_set_filter(&ops, NULL, 0, 1); 272 ret = ftrace_set_filter(&ops, NULL, 0, 1);
273 273
274 274
275 Sometimes more than one function has the same 275 Sometimes more than one function has the same name. To trace just a specific
276 function in this case, ftrace_set_filter_ip() 276 function in this case, ftrace_set_filter_ip() can be used.
277 277
278 .. code-block:: c 278 .. code-block:: c
279 279
280 ret = ftrace_set_filter_ip(&ops, ip, 0, 0); 280 ret = ftrace_set_filter_ip(&ops, ip, 0, 0);
281 281
282 Although the ip must be the address where the 282 Although the ip must be the address where the call to fentry or mcount is
283 located in the function. This function is used 283 located in the function. This function is used by perf and kprobes that
284 gets the ip address from the user (usually usi 284 gets the ip address from the user (usually using debug info from the kernel).
285 285
286 If a glob is used to set the filter, functions 286 If a glob is used to set the filter, functions can be added to a "notrace"
287 list that will prevent those functions from ca 287 list that will prevent those functions from calling the callback.
288 The "notrace" list takes precedence over the " 288 The "notrace" list takes precedence over the "filter" list. If the
289 two lists are non-empty and contain the same f 289 two lists are non-empty and contain the same functions, the callback will not
290 be called by any function. 290 be called by any function.
291 291
292 An empty "notrace" list means to allow all fun 292 An empty "notrace" list means to allow all functions defined by the filter
293 to be traced. 293 to be traced.
294 294
295 .. code-block:: c 295 .. code-block:: c
296 296
297 int ftrace_set_notrace(struct ftrace_ops *o 297 int ftrace_set_notrace(struct ftrace_ops *ops, unsigned char *buf,
298 int len, int reset); 298 int len, int reset);
299 299
300 This takes the same parameters as ftrace_set_f 300 This takes the same parameters as ftrace_set_filter() but will add the
301 functions it finds to not be traced. This is a 301 functions it finds to not be traced. This is a separate list from the
302 filter list, and this function does not modify 302 filter list, and this function does not modify the filter list.
303 303
304 A non-zero @reset will clear the "notrace" lis 304 A non-zero @reset will clear the "notrace" list before adding functions
305 that match @buf to it. 305 that match @buf to it.
306 306
307 Clearing the "notrace" list is the same as cle 307 Clearing the "notrace" list is the same as clearing the filter list
308 308
309 .. code-block:: c 309 .. code-block:: c
310 310
311 ret = ftrace_set_notrace(&ops, NULL, 0, 1); 311 ret = ftrace_set_notrace(&ops, NULL, 0, 1);
312 312
313 The filter and notrace lists may be changed at 313 The filter and notrace lists may be changed at any time. If only a set of
314 functions should call the callback, it is best 314 functions should call the callback, it is best to set the filters before
315 registering the callback. But the changes may 315 registering the callback. But the changes may also happen after the callback
316 has been registered. 316 has been registered.
317 317
318 If a filter is in place, and the @reset is non 318 If a filter is in place, and the @reset is non-zero, and @buf contains a
319 matching glob to functions, the switch will ha 319 matching glob to functions, the switch will happen during the time of
320 the ftrace_set_filter() call. At no time will 320 the ftrace_set_filter() call. At no time will all functions call the callback.
321 321
322 .. code-block:: c 322 .. code-block:: c
323 323
324 ftrace_set_filter(&ops, "schedule", strlen( 324 ftrace_set_filter(&ops, "schedule", strlen("schedule"), 1);
325 325
326 register_ftrace_function(&ops); 326 register_ftrace_function(&ops);
327 327
328 msleep(10); 328 msleep(10);
329 329
330 ftrace_set_filter(&ops, "try_to_wake_up", s 330 ftrace_set_filter(&ops, "try_to_wake_up", strlen("try_to_wake_up"), 1);
331 331
332 is not the same as: 332 is not the same as:
333 333
334 .. code-block:: c 334 .. code-block:: c
335 335
336 ftrace_set_filter(&ops, "schedule", strlen( 336 ftrace_set_filter(&ops, "schedule", strlen("schedule"), 1);
337 337
338 register_ftrace_function(&ops); 338 register_ftrace_function(&ops);
339 339
340 msleep(10); 340 msleep(10);
341 341
342 ftrace_set_filter(&ops, NULL, 0, 1); 342 ftrace_set_filter(&ops, NULL, 0, 1);
343 343
344 ftrace_set_filter(&ops, "try_to_wake_up", s 344 ftrace_set_filter(&ops, "try_to_wake_up", strlen("try_to_wake_up"), 0);
345 345
346 As the latter will have a short time where all 346 As the latter will have a short time where all functions will call
347 the callback, between the time of the reset, a 347 the callback, between the time of the reset, and the time of the
348 new setting of the filter. 348 new setting of the filter.
Linux® is a registered trademark of Linus Torvalds in the United States and other countries.
TOMOYO® is a registered trademark of NTT DATA CORPORATION.