blob: 83baf0a3250eae2ed21449dfe06129054f0c74a8 [file] [log] [blame]
Randy Dunlapb67ad182008-11-12 13:26:55 -08001If variable is of Type, use printk format specifier:
2---------------------------------------------------------
3 int %d or %x
4 unsigned int %u or %x
5 long %ld or %lx
6 unsigned long %lu or %lx
7 long long %lld or %llx
8 unsigned long long %llu or %llx
9 size_t %zu or %zx
10 ssize_t %zd or %zx
Geert Uytterhoevene8a7ba52015-04-15 16:17:17 -070011 s32 %d or %x
12 u32 %u or %x
13 s64 %lld or %llx
14 u64 %llu or %llx
15
16If <type> is dependent on a config option for its size (e.g., sector_t,
17blkcnt_t) or is architecture-dependent for its size (e.g., tcflag_t), use a
18format specifier of its largest possible type and explicitly cast to it.
19Example:
20
21 printk("test: sector number/total blocks: %llu/%llu\n",
22 (unsigned long long)sector, (unsigned long long)blockcount);
23
24Reminder: sizeof() result is of type size_t.
25
Rasmus Villemoesd7ec9a02015-11-06 16:30:35 -080026The kernel's printf does not support %n. For obvious reasons, floating
27point formats (%e, %f, %g, %a) are also not recognized. Use of any
28unsupported specifier or length qualifier results in a WARN and early
29return from vsnprintf.
Randy Dunlapb67ad182008-11-12 13:26:55 -080030
Andrew Murray04c55712011-06-15 12:57:09 -070031Raw pointer value SHOULD be printed with %p. The kernel supports
32the following extended format specifiers for pointer types:
33
Tobin C. Hardingae89bc62017-11-01 15:32:23 +110034Pointer Types:
35
36Pointers printed without a specifier extension (i.e unadorned %p) are
37hashed to give a unique identifier without leaking kernel addresses to user
38space. On 64 bit machines the first 32 bits are zeroed.
39
40 %p abcdef12 or 00000000abcdef12
41
Andrew Murray04c55712011-06-15 12:57:09 -070042Symbols/Function Pointers:
43
44 %pF versatile_init+0x0/0x110
45 %pf versatile_init
46 %pS versatile_init+0x0/0x110
Joe Perchesb0d33c22012-12-12 10:18:50 -080047 %pSR versatile_init+0x9/0x110
48 (with __builtin_extract_return_addr() translation)
Andrew Murray04c55712011-06-15 12:57:09 -070049 %ps versatile_init
50 %pB prev_fn_of_versatile_init+0x88/0x88
51
52 For printing symbols and function pointers. The 'S' and 's' specifiers
53 result in the symbol name with ('S') or without ('s') offsets. Where
54 this is used on a kernel without KALLSYMS - the symbol address is
55 printed instead.
56
57 The 'B' specifier results in the symbol name with offsets and should be
58 used when printing stack backtraces. The specifier takes into
59 consideration the effect of compiler optimisations which may occur
60 when tail-call's are used and marked with the noreturn GCC attribute.
61
62 On ia64, ppc64 and parisc64 architectures function pointers are
63 actually function descriptors which must first be resolved. The 'F' and
64 'f' specifiers perform this resolution and then provide the same
65 functionality as the 'S' and 's' specifiers.
66
67Kernel Pointers:
68
Tobin C. Hardingb4d4c262017-11-23 10:55:24 +110069 %pK 01234567 or 0123456789abcdef
Andrew Murray04c55712011-06-15 12:57:09 -070070
71 For printing kernel pointers which should be hidden from unprivileged
72 users. The behaviour of %pK depends on the kptr_restrict sysctl - see
73 Documentation/sysctl/kernel.txt for more details.
74
75Struct Resources:
76
77 %pr [mem 0x60000000-0x6fffffff flags 0x2200] or
78 [mem 0x0000000060000000-0x000000006fffffff flags 0x2200]
79 %pR [mem 0x60000000-0x6fffffff pref] or
80 [mem 0x0000000060000000-0x000000006fffffff pref]
81
82 For printing struct resources. The 'R' and 'r' specifiers result in a
83 printed resource with ('R') or without ('r') a decoded flags member.
Geert Uytterhoeven73306602015-04-15 16:17:14 -070084 Passed by reference.
Andrew Murray04c55712011-06-15 12:57:09 -070085
Joe Perchesaaf07622014-01-23 15:54:17 -080086Physical addresses types phys_addr_t:
Stepan Moskovchenko7d799212013-02-21 16:43:09 -080087
Joe Perchesaaf07622014-01-23 15:54:17 -080088 %pa[p] 0x01234567 or 0x0123456789abcdef
Stepan Moskovchenko7d799212013-02-21 16:43:09 -080089
90 For printing a phys_addr_t type (and its derivatives, such as
91 resource_size_t) which can vary based on build options, regardless of
92 the width of the CPU data path. Passed by reference.
93
Joe Perchesaaf07622014-01-23 15:54:17 -080094DMA addresses types dma_addr_t:
95
96 %pad 0x01234567 or 0x0123456789abcdef
97
98 For printing a dma_addr_t type which can vary based on build options,
99 regardless of the width of the CPU data path. Passed by reference.
100
Andy Shevchenko71dca952014-10-13 15:55:18 -0700101Raw buffer as an escaped string:
102
103 %*pE[achnops]
104
105 For printing raw buffer as an escaped string. For the following buffer
106
107 1b 62 20 5c 43 07 22 90 0d 5d
108
109 few examples show how the conversion would be done (the result string
110 without surrounding quotes):
111
112 %*pE "\eb \C\a"\220\r]"
113 %*pEhp "\x1bb \C\x07"\x90\x0d]"
114 %*pEa "\e\142\040\\\103\a\042\220\r\135"
115
116 The conversion rules are applied according to an optional combination
117 of flags (see string_escape_mem() kernel documentation for the
118 details):
119 a - ESCAPE_ANY
120 c - ESCAPE_SPECIAL
121 h - ESCAPE_HEX
122 n - ESCAPE_NULL
123 o - ESCAPE_OCTAL
124 p - ESCAPE_NP
125 s - ESCAPE_SPACE
126 By default ESCAPE_ANY_NP is used.
127
128 ESCAPE_ANY_NP is the sane choice for many cases, in particularly for
129 printing SSIDs.
130
131 If field width is omitted the 1 byte only will be escaped.
132
Andy Shevchenko31550a12012-07-30 14:40:27 -0700133Raw buffer as a hex string:
Martin Kletzander5e4ee7b2015-11-06 16:30:17 -0800134
Andy Shevchenko31550a12012-07-30 14:40:27 -0700135 %*ph 00 01 02 ... 3f
136 %*phC 00:01:02: ... :3f
137 %*phD 00-01-02- ... -3f
138 %*phN 000102 ... 3f
139
140 For printing a small buffers (up to 64 bytes long) as a hex string with
141 certain separator. For the larger buffers consider to use
142 print_hex_dump().
143
Andrew Murray04c55712011-06-15 12:57:09 -0700144MAC/FDDI addresses:
145
146 %pM 00:01:02:03:04:05
Andrei Emeltchenko76597ff92012-07-30 14:40:23 -0700147 %pMR 05:04:03:02:01:00
Andrew Murray04c55712011-06-15 12:57:09 -0700148 %pMF 00-01-02-03-04-05
149 %pm 000102030405
Andy Shevchenko7c591542012-10-04 17:12:33 -0700150 %pmR 050403020100
Andrew Murray04c55712011-06-15 12:57:09 -0700151
152 For printing 6-byte MAC/FDDI addresses in hex notation. The 'M' and 'm'
153 specifiers result in a printed address with ('M') or without ('m') byte
154 separators. The default byte separator is the colon (':').
155
156 Where FDDI addresses are concerned the 'F' specifier can be used after
157 the 'M' specifier to use dash ('-') separators instead of the default
158 separator.
159
Andrei Emeltchenko76597ff92012-07-30 14:40:23 -0700160 For Bluetooth addresses the 'R' specifier shall be used after the 'M'
161 specifier to use reversed byte order suitable for visual interpretation
162 of Bluetooth addresses which are in the little endian order.
163
Geert Uytterhoeven73306602015-04-15 16:17:14 -0700164 Passed by reference.
165
Andrew Murray04c55712011-06-15 12:57:09 -0700166IPv4 addresses:
167
168 %pI4 1.2.3.4
169 %pi4 001.002.003.004
Daniel Borkmann8ecada12013-06-28 15:49:39 +0200170 %p[Ii]4[hnbl]
Andrew Murray04c55712011-06-15 12:57:09 -0700171
172 For printing IPv4 dot-separated decimal addresses. The 'I4' and 'i4'
173 specifiers result in a printed address with ('i4') or without ('I4')
174 leading zeros.
175
176 The additional 'h', 'n', 'b', and 'l' specifiers are used to specify
177 host, network, big or little endian order addresses respectively. Where
178 no specifier is provided the default network/big endian order is used.
179
Geert Uytterhoeven73306602015-04-15 16:17:14 -0700180 Passed by reference.
181
Andrew Murray04c55712011-06-15 12:57:09 -0700182IPv6 addresses:
183
184 %pI6 0001:0002:0003:0004:0005:0006:0007:0008
185 %pi6 00010002000300040005000600070008
186 %pI6c 1:2:3:4:5:6:7:8
187
188 For printing IPv6 network-order 16-bit hex addresses. The 'I6' and 'i6'
189 specifiers result in a printed address with ('I6') or without ('i6')
190 colon-separators. Leading zeros are always used.
191
192 The additional 'c' specifier can be used with the 'I' specifier to
193 print a compressed IPv6 address as described by
194 http://tools.ietf.org/html/rfc5952
195
Geert Uytterhoeven73306602015-04-15 16:17:14 -0700196 Passed by reference.
197
Daniel Borkmann10679642013-06-28 19:49:39 +0200198IPv4/IPv6 addresses (generic, with port, flowinfo, scope):
199
200 %pIS 1.2.3.4 or 0001:0002:0003:0004:0005:0006:0007:0008
201 %piS 001.002.003.004 or 00010002000300040005000600070008
202 %pISc 1.2.3.4 or 1:2:3:4:5:6:7:8
203 %pISpc 1.2.3.4:12345 or [1:2:3:4:5:6:7:8]:12345
204 %p[Ii]S[pfschnbl]
205
206 For printing an IP address without the need to distinguish whether it's
207 of type AF_INET or AF_INET6, a pointer to a valid 'struct sockaddr',
208 specified through 'IS' or 'iS', can be passed to this format specifier.
209
210 The additional 'p', 'f', and 's' specifiers are used to specify port
211 (IPv4, IPv6), flowinfo (IPv6) and scope (IPv6). Ports have a ':' prefix,
212 flowinfo a '/' and scope a '%', each followed by the actual value.
213
214 In case of an IPv6 address the compressed IPv6 address as described by
215 http://tools.ietf.org/html/rfc5952 is being used if the additional
216 specifier 'c' is given. The IPv6 address is surrounded by '[', ']' in
217 case of additional specifiers 'p', 'f' or 's' as suggested by
218 https://tools.ietf.org/html/draft-ietf-6man-text-addr-representation-07
219
220 In case of IPv4 addresses, the additional 'h', 'n', 'b', and 'l'
221 specifiers can be used as well and are ignored in case of an IPv6
222 address.
223
Geert Uytterhoeven73306602015-04-15 16:17:14 -0700224 Passed by reference.
225
Daniel Borkmann10679642013-06-28 19:49:39 +0200226 Further examples:
227
228 %pISfc 1.2.3.4 or [1:2:3:4:5:6:7:8]/123456789
229 %pISsc 1.2.3.4 or [1:2:3:4:5:6:7:8]%1234567890
230 %pISpfc 1.2.3.4:12345 or [1:2:3:4:5:6:7:8]:12345/123456789
231
Andrew Murray04c55712011-06-15 12:57:09 -0700232UUID/GUID addresses:
233
234 %pUb 00010203-0405-0607-0809-0a0b0c0d0e0f
235 %pUB 00010203-0405-0607-0809-0A0B0C0D0E0F
236 %pUl 03020100-0504-0706-0809-0a0b0c0e0e0f
237 %pUL 03020100-0504-0706-0809-0A0B0C0E0E0F
238
239 For printing 16-byte UUID/GUIDs addresses. The additional 'l', 'L',
240 'b' and 'B' specifiers are used to specify a little endian order in
241 lower ('l') or upper case ('L') hex characters - and big endian order
242 in lower ('b') or upper case ('B') hex characters.
243
Rasmus Villemoesd181b712015-02-24 15:26:06 +0100244 Where no additional specifiers are used the default big endian
Andrew Murray04c55712011-06-15 12:57:09 -0700245 order with lower case hex characters will be printed.
246
Geert Uytterhoeven73306602015-04-15 16:17:14 -0700247 Passed by reference.
248
Al Viro4b6ccca2013-09-03 12:00:44 -0400249dentry names:
Martin Kletzander5e4ee7b2015-11-06 16:30:17 -0800250
Al Viro4b6ccca2013-09-03 12:00:44 -0400251 %pd{,2,3,4}
252 %pD{,2,3,4}
253
254 For printing dentry name; if we race with d_move(), the name might be
255 a mix of old and new ones, but it won't oops. %pd dentry is a safer
256 equivalent of %s dentry->d_name.name we used to use, %pd<n> prints
257 n last components. %pD does the same thing for struct file.
258
Geert Uytterhoeven73306602015-04-15 16:17:14 -0700259 Passed by reference.
260
Dmitry Monakhov1031bc52015-04-13 16:31:35 +0400261block_device names:
262
263 %pg sda, sda1 or loop0p1
264
265 For printing name of block_device pointers.
266
Andrew Murray04c55712011-06-15 12:57:09 -0700267struct va_format:
268
269 %pV
270
271 For printing struct va_format structures. These contain a format string
272 and va_list as follows:
273
274 struct va_format {
275 const char *fmt;
276 va_list *va;
277 };
278
Martin Kletzander5e4ee7b2015-11-06 16:30:17 -0800279 Implements a "recursive vsnprintf".
280
Andrew Murray04c55712011-06-15 12:57:09 -0700281 Do not use this feature without some mechanism to verify the
282 correctness of the format string and va_list arguments.
Randy Dunlapb67ad182008-11-12 13:26:55 -0800283
Geert Uytterhoeven73306602015-04-15 16:17:14 -0700284 Passed by reference.
285
Geert Uytterhoeven900cca22015-04-15 16:17:20 -0700286struct clk:
287
288 %pC pll1
289 %pCn pll1
Geert Uytterhoeven900cca22015-04-15 16:17:20 -0700290
291 For printing struct clk structures. '%pC' and '%pCn' print the name
292 (Common Clock Framework) or address (legacy clock framework) of the
Geert Uytterhoevenec7bea32018-06-01 11:28:22 +0200293 structure.
Geert Uytterhoeven900cca22015-04-15 16:17:20 -0700294
295 Passed by reference.
296
Wang Longd0724962015-02-26 03:28:25 +0000297bitmap and its derivatives such as cpumask and nodemask:
298
299 %*pb 0779
300 %*pbl 0,3-6,8-10
301
302 For printing bitmap and its derivatives such as cpumask and nodemask,
303 %*pb output the bitmap with field width as the number of bits and %*pbl
304 output the bitmap as range list with field width as the number of bits.
305
Linus Torvaldsd6a24d02015-04-18 11:10:49 -0400306 Passed by reference.
Randy Dunlapb67ad182008-11-12 13:26:55 -0800307
Vlastimil Babkaedf14cd2016-03-15 14:55:56 -0700308Flags bitfields such as page flags, gfp_flags:
309
310 %pGp referenced|uptodate|lru|active|private
311 %pGg GFP_USER|GFP_DMA32|GFP_NOWARN
312 %pGv read|exec|mayread|maywrite|mayexec|denywrite
313
314 For printing flags bitfields as a collection of symbolic constants that
315 would construct the value. The type of flags is given by the third
316 character. Currently supported are [p]age flags, [v]ma_flags (both
317 expect unsigned long *) and [g]fp_flags (expects gfp_t *). The flag
318 names and print order depends on the particular type.
319
320 Note that this format should not be used directly in TP_printk() part
321 of a tracepoint. Instead, use the show_*_flags() functions from
322 <trace/events/mmflags.h>.
323
324 Passed by reference.
325
Martin Kletzander5e4ee7b2015-11-06 16:30:17 -0800326Network device features:
327
328 %pNF 0x000000000000c000
329
330 For printing netdev_features_t.
331
332 Passed by reference.
333
Rasmus Villemoesd7ec9a02015-11-06 16:30:35 -0800334If you add other %p extensions, please extend lib/test_printf.c with
335one or more test cases, if at all feasible.
Martin Kletzander5e4ee7b2015-11-06 16:30:17 -0800336
Martin Kletzander5e4ee7b2015-11-06 16:30:17 -0800337
Randy Dunlapb67ad182008-11-12 13:26:55 -0800338Thank you for your cooperation and attention.
339
340
Randy Dunlap755727b2013-03-08 12:43:35 -0800341By Randy Dunlap <rdunlap@infradead.org> and
Andrew Murray04c55712011-06-15 12:57:09 -0700342Andrew Murray <amurray@mpc-data.co.uk>