]>
Commit | Line | Data |
---|---|---|
c3e270f4 FB |
1 | --- |
2 | title: Coding Style | |
4cdca0af | 3 | category: Contributing |
b41a3f66 | 4 | layout: default |
0aff7b75 | 5 | SPDX-License-Identifier: LGPL-2.1-or-later |
c3e270f4 FB |
6 | --- |
7 | ||
c1d3483d | 8 | # Coding Style |
82143987 | 9 | |
8c9289e7 LP |
10 | ## Formatting |
11 | ||
3b69b18f ZJS |
12 | - 8ch indent, no tabs, except for files in `man/` which are 2ch indent, and |
13 | still no tabs, and shell scripts, which are 4ch indent, and no tabs either. | |
82143987 | 14 | |
8c9289e7 LP |
15 | - We prefer `/* comments */` over `// comments` in code you commit, |
16 | please. This way `// comments` are left for developers to use for local, | |
17 | temporary commenting of code for debug purposes (i.e. uncommittable stuff), | |
18 | making such comments easily discernible from explanatory, documenting code | |
19 | comments (i.e. committable stuff). | |
82143987 FA |
20 | |
21 | - Don't break code lines too eagerly. We do **not** force line breaks at 80ch, | |
22 | all of today's screens should be much larger than that. But then again, don't | |
c90ee834 | 23 | overdo it, ~109ch should be enough really. The `.editorconfig`, `.vimrc` and |
82143987 | 24 | `.dir-locals.el` files contained in the repository will set this limit up for |
3b69b18f ZJS |
25 | you automatically, if you let them (as well as a few other things). Please |
26 | note that emacs loads `.dir-locals.el` automatically, but vim needs to be | |
27 | configured to load `.vimrc`, see that file for instructions. | |
82143987 | 28 | |
7489ccc3 LB |
29 | - If you break a function declaration over multiple lines, do it like this: |
30 | ||
31 | ```c | |
32 | void some_function( | |
33 | int foo, | |
34 | bool bar, | |
35 | char baz) { | |
36 | ||
37 | int a, b, c; | |
38 | ``` | |
39 | ||
cf33b707 LP |
40 | (i.e. use double indentation — 16 spaces — for the parameter list.) |
41 | ||
8c9289e7 LP |
42 | - Try to write this: |
43 | ||
44 | ```c | |
45 | void foo() { | |
46 | } | |
47 | ``` | |
48 | ||
49 | instead of this: | |
50 | ||
51 | ```c | |
52 | void foo() | |
53 | { | |
54 | } | |
55 | ``` | |
56 | ||
57 | - Single-line `if` blocks should not be enclosed in `{}`. Write this: | |
58 | ||
59 | ```c | |
60 | if (foobar) | |
61 | waldo(); | |
62 | ``` | |
63 | ||
64 | instead of this: | |
65 | ||
66 | ```c | |
67 | if (foobar) { | |
68 | waldo(); | |
69 | } | |
70 | ``` | |
71 | ||
72 | - Do not write `foo ()`, write `foo()`. | |
e8a587dc | 73 | |
4dbad977 AW |
74 | - `else` blocks should generally start on the same line as the closing `}`: |
75 | ```c | |
76 | if (foobar) { | |
77 | find(); | |
78 | waldo(); | |
79 | } else | |
80 | dont_find_waldo(); | |
81 | ``` | |
8c9289e7 | 82 | |
e28770e3 LP |
83 | - Please define flags types like this: |
84 | ||
85 | ```c | |
86 | typedef enum FoobarFlags { | |
87 | FOOBAR_QUUX = 1 << 0, | |
88 | FOOBAR_WALDO = 1 << 1, | |
89 | FOOBAR_XOXO = 1 << 2, | |
90 | … | |
91 | } FoobarFlags; | |
92 | ``` | |
93 | ||
94 | i.e. use an enum for it, if possible. Indicate bit values via `1 <<` | |
95 | expressions, and align them vertically. Define both an enum and a type for | |
96 | it. | |
97 | ||
98 | - If you define (non-flags) enums, follow this template: | |
99 | ||
100 | ```c | |
101 | typedef enum FoobarMode { | |
102 | FOOBAR_AAA, | |
103 | FOOBAR_BBB, | |
104 | FOOBAR_CCC, | |
105 | … | |
106 | _FOOBAR_MAX, | |
107 | _FOOBAR_INVALID = -EINVAL, | |
108 | } FoobarMode; | |
109 | ``` | |
110 | ||
111 | i.e. define a `_MAX` enum for the largest defined enum value, plus one. Since | |
112 | this is not a regular enum value, prefix it with `_`. Also, define a special | |
113 | "invalid" enum value, and set it to `-EINVAL`. That way the enum type can | |
114 | safely be used to propagate conversion errors. | |
115 | ||
116 | - If you define an enum in a public API, be extra careful, as the size of the | |
117 | enum might change when new values are added, which would break ABI | |
118 | compatibility. Since we typically want to allow adding new enum values to an | |
119 | existing enum type with later API versions, please use the | |
120 | `_SD_ENUM_FORCE_S64()` macro in the enum definition, which forces the size of | |
121 | the enum to be signed 64bit wide. | |
122 | ||
b4f12824 | 123 | ## Code Organization and Semantics |
8c9289e7 | 124 | |
40f55f69 LP |
125 | - For our codebase we intend to use ISO C11 *with* GNU extensions (aka |
126 | "gnu11"). Public APIs (i.e. those we expose via `libsystemd.so` | |
127 | i.e. `systemd/sd-*.h`) should only use ISO C89 however (with a very limited | |
128 | set of conservative and common extensions, such as fixed size integer types | |
129 | from `<inttypes.h>`), so that we don't force consuming programs into C11 | |
130 | mode. (This discrepancy in particular means one thing: internally we use C99 | |
131 | `bool` booleans, externally C89-compatible `int` booleans which generally | |
132 | have different size in memory and slightly different semantics, also see | |
133 | below.) Both for internal and external code it's OK to use even newer | |
134 | features and GCC extension than "gnu11", as long as there's reasonable | |
135 | fallback #ifdeffery in place to ensure compatibility is retained with older | |
136 | compilers. | |
137 | ||
78e5b4d7 LP |
138 | - Please name structures in `PascalCase` (with exceptions, such as public API |
139 | structs), variables and functions in `snake_case`. | |
82143987 | 140 | |
b4f12824 LP |
141 | - Avoid static variables, except for caches and very few other cases. Think |
142 | about thread-safety! While most of our code is never used in threaded | |
143 | environments, at least the library code should make sure it works correctly | |
144 | in them. Instead of doing a lot of locking for that, we tend to prefer using | |
145 | TLS to do per-thread caching (which only works for small, fixed-size cache | |
146 | objects), or we disable caching for any thread that is not the main | |
147 | thread. Use `is_main_thread()` to detect whether the calling thread is the | |
148 | main thread. | |
82143987 | 149 | |
82143987 | 150 | - Do not write functions that clobber call-by-reference variables on |
b4f12824 | 151 | failure. Use temporary variables for these cases and change the passed in |
cf33b707 LP |
152 | variables only on success. The rule is: never clobber return parameters on |
153 | failure, always initialize return parameters on success. | |
154 | ||
155 | - Typically, function parameters fit into three categories: input parameters, | |
156 | mutable objects, and call-by-reference return parameters. Input parameters | |
157 | should always carry suitable "const" declarators if they are pointers, to | |
158 | indicate they are input-only and not changed by the function. Return | |
159 | parameters are best prefixed with "ret_", to clarify they are return | |
160 | parameters. (Conversely, please do not prefix parameters that aren't | |
161 | output-only with "ret_", in particular not mutable parameters that are both | |
162 | input as well as output). Example: | |
163 | ||
164 | ```c | |
165 | static int foobar_frobnicate( | |
166 | Foobar* object, /* the associated mutable object */ | |
167 | const char *input, /* immutable input parameter */ | |
168 | char **ret_frobnicated) { /* return parameter */ | |
169 | … | |
170 | return 0; | |
171 | } | |
172 | ``` | |
82143987 | 173 | |
82143987 | 174 | - The order in which header files are included doesn't matter too |
b4f12824 LP |
175 | much. systemd-internal headers must not rely on an include order, so it is |
176 | safe to include them in any order possible. However, to not clutter global | |
177 | includes, and to make sure internal definitions will not affect global | |
178 | headers, please always include the headers of external components first | |
179 | (these are all headers enclosed in <>), followed by our own exported headers | |
180 | (usually everything that's prefixed by `sd-`), and then followed by internal | |
181 | headers. Furthermore, in all three groups, order all includes alphabetically | |
82143987 FA |
182 | so duplicate includes can easily be detected. |
183 | ||
b4f12824 LP |
184 | - Please avoid using global variables as much as you can. And if you do use |
185 | them make sure they are static at least, instead of exported. Especially in | |
186 | library-like code it is important to avoid global variables. Why are global | |
187 | variables bad? They usually hinder generic reusability of code (since they | |
188 | break in threaded programs, and usually would require locking there), and as | |
189 | the code using them has side-effects make programs non-transparent. That | |
190 | said, there are many cases where they explicitly make a lot of sense, and are | |
191 | OK to use. For example, the log level and target in `log.c` is stored in a | |
192 | global variable, and that's OK and probably expected by most. Also in many | |
193 | cases we cache data in global variables. If you add more caches like this, | |
194 | please be careful however, and think about threading. Only use static | |
195 | variables if you are sure that thread-safety doesn't matter in your | |
196 | case. Alternatively, consider using TLS, which is pretty easy to use with | |
197 | gcc's `thread_local` concept. It's also OK to store data that is inherently | |
198 | global in global variables, for example data parsed from command lines, see | |
82143987 FA |
199 | below. |
200 | ||
82143987 FA |
201 | - Our focus is on the GNU libc (glibc), not any other libcs. If other libcs are |
202 | incompatible with glibc it's on them. However, if there are equivalent POSIX | |
203 | and Linux/GNU-specific APIs, we generally prefer the POSIX APIs. If there | |
204 | aren't, we are happy to use GNU or Linux APIs, and expect non-GNU | |
205 | implementations of libc to catch up with glibc. | |
206 | ||
78e5b4d7 LP |
207 | ## Using C Constructs |
208 | ||
756755d0 | 209 | - Allocate local variables where it makes sense: at the top of the block, or at |
9214f299 ZJS |
210 | the point where they can be initialized. Avoid huge variable declaration |
211 | lists at the top of the function. | |
212 | ||
213 | As an exception, `r` is typically used for a local state variable, but should | |
214 | almost always be declared as the last variable at the top of the function. | |
78e5b4d7 LP |
215 | |
216 | ```c | |
217 | { | |
9214f299 | 218 | uint64_t a; |
756755d0 | 219 | int r; |
78e5b4d7 | 220 | |
9214f299 ZJS |
221 | r = frobnicate(&a); |
222 | if (r < 0) | |
223 | … | |
224 | ||
225 | uint64_t b = a + 1, c; | |
756755d0 | 226 | |
9214f299 | 227 | r = foobarify(a, b, &c); |
756755d0 ZJS |
228 | if (r < 0) |
229 | … | |
9214f299 ZJS |
230 | |
231 | const char *pretty = prettify(a, b, c); | |
232 | … | |
78e5b4d7 LP |
233 | } |
234 | ``` | |
235 | ||
9214f299 ZJS |
236 | - Do not mix multiple variable definitions with function invocations or |
237 | complicated expressions: | |
78e5b4d7 LP |
238 | |
239 | ```c | |
240 | { | |
78e5b4d7 | 241 | uint64_t x = 7; |
756755d0 ZJS |
242 | int a; |
243 | ||
244 | a = foobar(); | |
78e5b4d7 LP |
245 | } |
246 | ``` | |
247 | ||
756755d0 | 248 | instead of: |
78e5b4d7 LP |
249 | |
250 | ```c | |
251 | { | |
756755d0 | 252 | int a = foobar(); |
78e5b4d7 | 253 | uint64_t x = 7; |
78e5b4d7 LP |
254 | } |
255 | ``` | |
256 | ||
756755d0 | 257 | - Use `goto` for cleaning up, and only use it for that. I.e. you may only jump |
78e5b4d7 LP |
258 | to the end of a function, and little else. Never jump backwards! |
259 | ||
260 | - To minimize strict aliasing violations, we prefer unions over casting. | |
261 | ||
262 | - Instead of using `memzero()`/`memset()` to initialize structs allocated on | |
263 | the stack, please try to use c99 structure initializers. It's short, prettier | |
264 | and actually even faster at execution. Hence: | |
265 | ||
266 | ```c | |
267 | struct foobar t = { | |
268 | .foo = 7, | |
269 | .bar = "bazz", | |
270 | }; | |
271 | ``` | |
272 | ||
273 | instead of: | |
274 | ||
275 | ```c | |
276 | struct foobar t; | |
277 | zero(t); | |
278 | t.foo = 7; | |
279 | t.bar = "bazz"; | |
280 | ``` | |
281 | ||
282 | - To implement an endless loop, use `for (;;)` rather than `while (1)`. The | |
283 | latter is a bit ugly anyway, since you probably really meant `while | |
284 | (true)`. To avoid the discussion what the right always-true expression for an | |
285 | infinite while loop is, our recommendation is to simply write it without any | |
286 | such expression by using `for (;;)`. | |
287 | ||
288 | - To determine the length of a constant string `"foo"`, don't bother with | |
289 | `sizeof("foo")-1`, please use `strlen()` instead (both gcc and clang optimize | |
290 | the call away for fixed strings). The only exception is when declaring an | |
9214f299 | 291 | array. In that case use `STRLEN()`, which evaluates to a static constant and |
78e5b4d7 LP |
292 | doesn't force the compiler to create a VLA. |
293 | ||
b5bd7a29 LP |
294 | - Please use C's downgrade-to-bool feature only for expressions that are |
295 | actually booleans (or "boolean-like"), and not for variables that are really | |
296 | numeric. Specifically, if you have an `int b` and it's only used in a boolean | |
297 | sense, by all means check its state with `if (b) …` — but if `b` can actually | |
298 | have more than two semantic values, and you want to compare for non-zero, | |
d238709c | 299 | then please write that explicitly with `if (b != 0) …`. This helps readability |
b5bd7a29 LP |
300 | as the value range and semantical behaviour is directly clear from the |
301 | condition check. As a special addition: when dealing with pointers which you | |
302 | want to check for non-NULL-ness, you may also use downgrade-to-bool feature. | |
303 | ||
304 | - Please do not use yoda comparisons, i.e. please prefer the more readable `if | |
305 | (a == 7)` over the less readable `if (7 == a)`. | |
306 | ||
c159efe3 LP |
307 | ## Destructors |
308 | ||
309 | - The destructors always deregister the object from the next bigger object, not | |
310 | the other way around. | |
311 | ||
312 | - For robustness reasons, destructors should be able to destruct | |
313 | half-initialized objects, too. | |
314 | ||
315 | - When you define a destructor or `unref()` call for an object, please accept a | |
316 | `NULL` object and simply treat this as NOP. This is similar to how libc | |
317 | `free()` works, which accepts `NULL` pointers and becomes a NOP for them. By | |
318 | following this scheme a lot of `if` checks can be removed before invoking | |
319 | your destructor, which makes the code substantially more readable and robust. | |
320 | ||
321 | - Related to this: when you define a destructor or `unref()` call for an | |
322 | object, please make it return the same type it takes and always return `NULL` | |
323 | from it. This allows writing code like this: | |
324 | ||
325 | ```c | |
326 | p = foobar_unref(p); | |
327 | ``` | |
328 | ||
2d1b9281 | 329 | which will always work regardless if `p` is initialized or not, and |
c159efe3 LP |
330 | guarantees that `p` is `NULL` afterwards, all in just one line. |
331 | ||
e8a587dc LP |
332 | ## Common Function Naming |
333 | ||
334 | - Name destructor functions that destroy an object in full freeing all its | |
335 | memory and associated resources (and thus invalidating the pointer to it) | |
336 | `xyz_free()`. Example: `strv_free()`. | |
337 | ||
338 | - Name destructor functions that destroy only the referenced content of an | |
339 | object but leave the object itself allocated `xyz_done()`. If it resets all | |
340 | fields so that the object can be reused later call it `xyz_clear()`. | |
341 | ||
342 | - Functions that decrease the reference counter of an object by one should be | |
343 | called `xyz_unref()`. Example: `json_variant_unref()`. Functions that | |
344 | increase the reference counter by one should be called `xyz_ref()`. Example: | |
345 | `json_variant_ref()` | |
346 | ||
b065e1f1 LP |
347 | ## Error Handling |
348 | ||
349 | - Error codes are returned as negative `Exxx`. e.g. `return -EINVAL`. There are | |
350 | some exceptions: for constructors, it is OK to return `NULL` on OOM. For | |
351 | lookup functions, `NULL` is fine too for "not found". | |
352 | ||
353 | Be strict with this. When you write a function that can fail due to more than | |
354 | one cause, it *really* should have an `int` as the return value for the error | |
355 | code. | |
356 | ||
947796ea LP |
357 | - libc system calls typically return -1 on error (with the error code in |
358 | `errno`), and >= 0 on success. Use the RET_NERRNO() helper if you are looking | |
359 | for a simple way to convert this libc style error returning into systemd | |
360 | style error returning. e.g. | |
361 | ||
362 | ```c | |
363 | … | |
364 | r = RET_NERRNO(unlink(t)); | |
365 | … | |
366 | ``` | |
367 | ||
368 | or | |
369 | ||
370 | ```c | |
371 | … | |
372 | r = RET_NERRNO(open("/some/file", O_RDONLY|O_CLOEXEC)); | |
373 | … | |
374 | ``` | |
375 | ||
b065e1f1 LP |
376 | - Do not bother with error checking whether writing to stdout/stderr worked. |
377 | ||
378 | - Do not log errors from "library" code, only do so from "main program" | |
379 | code. (With one exception: it is OK to log with DEBUG level from any code, | |
380 | with the exception of maybe inner loops). | |
381 | ||
382 | - In public API calls, you **must** validate all your input arguments for | |
383 | programming error with `assert_return()` and return a sensible return | |
384 | code. In all other calls, it is recommended to check for programming errors | |
385 | with a more brutal `assert()`. We are more forgiving to public users than for | |
386 | ourselves! Note that `assert()` and `assert_return()` really only should be | |
387 | used for detecting programming errors, not for runtime errors. `assert()` and | |
be7148eb | 388 | `assert_return()` by usage of `_likely_()` inform the compiler that it should |
b065e1f1 LP |
389 | not expect these checks to fail, and they inform fellow programmers about the |
390 | expected validity and range of parameters. | |
391 | ||
392 | - When you invoke certain calls like `unlink()`, or `mkdir_p()` and you know it | |
393 | is safe to ignore the error it might return (because a later call would | |
394 | detect the failure anyway, or because the error is in an error path and you | |
395 | thus couldn't do anything about it anyway), then make this clear by casting | |
396 | the invocation explicitly to `(void)`. Code checks like Coverity understand | |
397 | that, and will not complain about ignored error codes. Hence, please use | |
398 | this: | |
399 | ||
400 | ```c | |
401 | (void) unlink("/foo/bar/baz"); | |
402 | ``` | |
403 | ||
404 | instead of just this: | |
405 | ||
406 | ```c | |
407 | unlink("/foo/bar/baz"); | |
408 | ``` | |
409 | ||
800d0802 AZ |
410 | When returning from a `void` function, you may also want to shorten the error |
411 | path boilerplate by returning a function invocation cast to `(void)` like so: | |
412 | ||
413 | ```c | |
414 | if (condition_not_met) | |
415 | return (void) log_tests_skipped("Cannot run ..."); | |
416 | ``` | |
417 | ||
b065e1f1 LP |
418 | Don't cast function calls to `(void)` that return no error |
419 | conditions. Specifically, the various `xyz_unref()` calls that return a | |
420 | `NULL` object shouldn't be cast to `(void)`, since not using the return value | |
421 | does not hide any errors. | |
422 | ||
423 | - When returning a return code from `main()`, please preferably use | |
424 | `EXIT_FAILURE` and `EXIT_SUCCESS` as defined by libc. | |
425 | ||
96f6cfbf LP |
426 | ## Logging |
427 | ||
428 | - For every function you add, think about whether it is a "logging" function or | |
cf33b707 | 429 | a "non-logging" function. "Logging" functions do (non-debug) logging on their |
f223fd6a | 430 | own, "non-logging" functions never log on their own (except at debug level) |
cf33b707 LP |
431 | and expect their callers to log. All functions in "library" code, i.e. in |
432 | `src/shared/` and suchlike must be "non-logging". Every time a "logging" | |
433 | function calls a "non-logging" function, it should log about the resulting | |
434 | errors. If a "logging" function calls another "logging" function, then it | |
435 | should not generate log messages, so that log messages are not generated | |
436 | twice for the same errors. (Note that debug level logging — at syslog level | |
437 | `LOG_DEBUG` — is not considered logging in this context, debug logging is | |
438 | generally always fine and welcome.) | |
96f6cfbf LP |
439 | |
440 | - If possible, do a combined log & return operation: | |
441 | ||
442 | ```c | |
443 | r = operation(...); | |
444 | if (r < 0) | |
445 | return log_(error|warning|notice|...)_errno(r, "Failed to ...: %m"); | |
446 | ``` | |
447 | ||
448 | If the error value is "synthetic", i.e. it was not received from | |
449 | the called function, use `SYNTHETIC_ERRNO` wrapper to tell the logging | |
450 | system to not log the errno value, but still return it: | |
451 | ||
452 | ```c | |
453 | n = read(..., s, sizeof s); | |
454 | if (n != sizeof s) | |
455 | return log_error_errno(SYNTHETIC_ERRNO(EIO), "Failed to read ..."); | |
456 | ``` | |
457 | ||
04858240 LP |
458 | ## Memory Allocation |
459 | ||
460 | - Always check OOM. There is no excuse. In program code, you can use | |
461 | `log_oom()` for then printing a short message, but not in "library" code. | |
462 | ||
463 | - Avoid fixed-size string buffers, unless you really know the maximum size and | |
756755d0 | 464 | that maximum size is small. It is often nicer to use dynamic memory, |
e3bde912 LP |
465 | `alloca_safe()` or VLAs. If you do allocate fixed-size strings on the stack, |
466 | then it is probably only OK if you either use a maximum size such as | |
467 | `LINE_MAX`, or count in detail the maximum size a string can | |
468 | have. (`DECIMAL_STR_MAX` and `DECIMAL_STR_WIDTH` macros are your friends for | |
469 | this!) | |
04858240 LP |
470 | |
471 | Or in other words, if you use `char buf[256]` then you are likely doing | |
472 | something wrong! | |
473 | ||
474 | - Make use of `_cleanup_free_` and friends. It makes your code much nicer to | |
475 | read (and shorter)! | |
476 | ||
e3bde912 LP |
477 | - Do not use `alloca()`, `strdupa()` or `strndupa()` directly. Use |
478 | `alloca_safe()`, `strdupa_safe()` or `strndupa_safe()` instead. (The | |
479 | difference is that the latter include an assertion that the specified size is | |
480 | below a safety threshold, so that the program rather aborts than runs into | |
481 | possible stack overruns.) | |
482 | ||
483 | - Use `alloca_safe()`, but never forget that it is not OK to invoke | |
484 | `alloca_safe()` within a loop or within function call | |
485 | parameters. `alloca_safe()` memory is released at the end of a function, and | |
486 | not at the end of a `{}` block. Thus, if you invoke it in a loop, you keep | |
487 | increasing the stack pointer without ever releasing memory again. (VLAs have | |
488 | better behavior in this case, so consider using them as an alternative.) | |
489 | Regarding not using `alloca_safe()` within function parameters, see the BUGS | |
490 | section of the `alloca(3)` man page. | |
04858240 LP |
491 | |
492 | - If you want to concatenate two or more strings, consider using `strjoina()` | |
493 | or `strjoin()` rather than `asprintf()`, as the latter is a lot slower. This | |
494 | matters particularly in inner loops (but note that `strjoina()` cannot be | |
495 | used there). | |
496 | ||
4467d393 LP |
497 | ## Runtime Behaviour |
498 | ||
499 | - Avoid leaving long-running child processes around, i.e. `fork()`s that are | |
500 | not followed quickly by an `execv()` in the child. Resource management is | |
501 | unclear in this case, and memory CoW will result in unexpected penalties in | |
502 | the parent much, much later on. | |
503 | ||
504 | - Don't block execution for arbitrary amounts of time using `usleep()` or a | |
505 | similar call, unless you really know what you do. Just "giving something some | |
506 | time", or so is a lazy excuse. Always wait for the proper event, instead of | |
507 | doing time-based poll loops. | |
508 | ||
509 | - Whenever installing a signal handler, make sure to set `SA_RESTART` for it, | |
510 | so that interrupted system calls are automatically restarted, and we minimize | |
511 | hassles with handling `EINTR` (in particular as `EINTR` handling is pretty | |
512 | broken on Linux). | |
513 | ||
514 | - When applying C-style unescaping as well as specifier expansion on the same | |
c90b6abc | 515 | string, always apply the C-style unescaping first, followed by the specifier |
4467d393 LP |
516 | expansion. When doing the reverse, make sure to escape `%` in specifier-style |
517 | first (i.e. `%` → `%%`), and then do C-style escaping where necessary. | |
518 | ||
519 | - Be exceptionally careful when formatting and parsing floating point | |
520 | numbers. Their syntax is locale dependent (i.e. `5.000` in en_US is generally | |
521 | understood as 5, while in de_DE as 5000.). | |
522 | ||
523 | - Make sure to enforce limits on every user controllable resource. If the user | |
524 | can allocate resources in your code, your code must enforce some form of | |
525 | limits after which it will refuse operation. It's fine if it is hard-coded | |
526 | (at least initially), but it needs to be there. This is particularly | |
527 | important for objects that unprivileged users may allocate, but also matters | |
6ae11e12 | 528 | for everything else any user may allocate. |
4467d393 | 529 | |
f42c1cd4 LP |
530 | ## Types |
531 | ||
532 | - Think about the types you use. If a value cannot sensibly be negative, do not | |
533 | use `int`, but use `unsigned`. | |
534 | ||
535 | - Use `char` only for actual characters. Use `uint8_t` or `int8_t` when you | |
536 | actually mean a byte-sized signed or unsigned integers. When referring to a | |
537 | generic byte, we generally prefer the unsigned variant `uint8_t`. Do not use | |
538 | types based on `short`. They *never* make sense. Use `int`, `long`, `long | |
539 | long`, all in unsigned and signed fashion, and the fixed-size types | |
540 | `uint8_t`, `uint16_t`, `uint32_t`, `uint64_t`, `int8_t`, `int16_t`, `int32_t` | |
541 | and so on, as well as `size_t`, but nothing else. Do not use kernel types | |
542 | like `u32` and so on, leave that to the kernel. | |
543 | ||
544 | - Stay uniform. For example, always use `usec_t` for time values. Do not mix | |
545 | `usec` and `msec`, and `usec` and whatnot. | |
546 | ||
547 | - Never use the `off_t` type, and particularly avoid it in public APIs. It's | |
548 | really weirdly defined, as it usually is 64-bit and we don't support it any | |
549 | other way, but it could in theory also be 32-bit. Which one it is depends on | |
550 | a compiler switch chosen by the compiled program, which hence corrupts APIs | |
551 | using it unless they can also follow the program's choice. Moreover, in | |
552 | systemd we should parse values the same way on all architectures and cannot | |
553 | expose `off_t` values over D-Bus. To avoid any confusion regarding conversion | |
554 | and ABIs, always use simply `uint64_t` directly. | |
555 | ||
556 | - Unless you allocate an array, `double` is always a better choice than | |
557 | `float`. Processors speak `double` natively anyway, so there is no speed | |
558 | benefit, and on calls like `printf()` `float`s get promoted to `double`s | |
559 | anyway, so there is no point. | |
560 | ||
561 | - Use the bool type for booleans, not integers. One exception: in public | |
562 | headers (i.e those in `src/systemd/sd-*.h`) use integers after all, as `bool` | |
40f55f69 LP |
563 | is C99 and in our public APIs we try to stick to C89 (with a few extensions; |
564 | also see above). | |
f42c1cd4 | 565 | |
3b75e079 LP |
566 | ## Deadlocks |
567 | ||
38b38500 | 568 | - Do not issue NSS requests (that includes user name and hostname lookups) |
3b75e079 LP |
569 | from PID 1 as this might trigger deadlocks when those lookups involve |
570 | synchronously talking to services that we would need to start up. | |
571 | ||
572 | - Do not synchronously talk to any other service from PID 1, due to risk of | |
573 | deadlocks. | |
574 | ||
25553cd9 LP |
575 | ## File Descriptors |
576 | ||
577 | - When you allocate a file descriptor, it should be made `O_CLOEXEC` right from | |
578 | the beginning, as none of our files should leak to forked binaries by | |
579 | default. Hence, whenever you open a file, `O_CLOEXEC` must be specified, | |
580 | right from the beginning. This also applies to sockets. Effectively, this | |
581 | means that all invocations to: | |
582 | ||
583 | - `open()` must get `O_CLOEXEC` passed, | |
584 | - `socket()` and `socketpair()` must get `SOCK_CLOEXEC` passed, | |
585 | - `recvmsg()` must get `MSG_CMSG_CLOEXEC` set, | |
586 | - `F_DUPFD_CLOEXEC` should be used instead of `F_DUPFD`, and so on, | |
587 | - invocations of `fopen()` should take `e`. | |
588 | ||
589 | - It's a good idea to use `O_NONBLOCK` when opening 'foreign' regular files, | |
590 | i.e. file system objects that are supposed to be regular files whose paths | |
d0515a28 | 591 | were specified by the user and hence might actually refer to other types of |
25553cd9 LP |
592 | file system objects. This is a good idea so that we don't end up blocking on |
593 | 'strange' file nodes, for example if the user pointed us to a FIFO or device | |
594 | node which may block when opening. Moreover even for actual regular files | |
595 | `O_NONBLOCK` has a benefit: it bypasses any mandatory lock that might be in | |
596 | effect on the regular file. If in doubt consider turning off `O_NONBLOCK` | |
597 | again after opening. | |
598 | ||
996f119d LP |
599 | ## Command Line |
600 | ||
601 | - If you parse a command line, and want to store the parsed parameters in | |
602 | global variables, please consider prefixing their names with `arg_`. We have | |
603 | been following this naming rule in most of our tools, and we should continue | |
604 | to do so, as it makes it easy to identify command line parameter variables, | |
605 | and makes it clear why it is OK that they are global variables. | |
606 | ||
607 | - Command line option parsing: | |
608 | - Do not print full `help()` on error, be specific about the error. | |
609 | - Do not print messages to stdout on error. | |
610 | - Do not POSIX_ME_HARDER unless necessary, i.e. avoid `+` in option string. | |
611 | ||
56380761 LP |
612 | ## Exporting Symbols |
613 | ||
614 | - Variables and functions **must** be static, unless they have a prototype, and | |
615 | are supposed to be exported. | |
616 | ||
617 | - Public API calls (i.e. functions exported by our shared libraries) | |
618 | must be marked `_public_` and need to be prefixed with `sd_`. No | |
619 | other functions should be prefixed like that. | |
620 | ||
621 | - When exposing public C APIs, be careful what function parameters you make | |
622 | `const`. For example, a parameter taking a context object should probably not | |
623 | be `const`, even if you are writing an otherwise read-only accessor function | |
624 | for it. The reason is that making it `const` fixates the contract that your | |
625 | call won't alter the object ever, as part of the API. However, that's often | |
626 | quite a promise, given that this even prohibits object-internal caching or | |
627 | lazy initialization of object variables. Moreover, it's usually not too | |
628 | useful for client applications. Hence, please be careful and avoid `const` on | |
629 | object parameters, unless you are very sure `const` is appropriate. | |
630 | ||
971dfffa LP |
631 | ## Referencing Concepts |
632 | ||
82143987 FA |
633 | - When referring to a configuration file option in the documentation and such, |
634 | please always suffix it with `=`, to indicate that it is a configuration file | |
635 | setting. | |
636 | ||
637 | - When referring to a command line option in the documentation and such, please | |
638 | always prefix with `--` or `-` (as appropriate), to indicate that it is a | |
639 | command line option. | |
640 | ||
641 | - When referring to a file system path that is a directory, please always | |
642 | suffix it with `/`, to indicate that it is a directory, not a regular file | |
643 | (or other file system object). | |
644 | ||
2d0dce2a LP |
645 | ## Functions to Avoid |
646 | ||
647 | - Use `memzero()` or even better `zero()` instead of `memset(..., 0, ...)` | |
648 | ||
649 | - Please use `streq()` and `strneq()` instead of `strcmp()`, `strncmp()` where | |
650 | applicable (i.e. wherever you just care about equality/inequality, not about | |
651 | the sorting order). | |
652 | ||
653 | - Never use `strtol()`, `atoi()` and similar calls. Use `safe_atoli()`, | |
654 | `safe_atou32()` and suchlike instead. They are much nicer to use in most | |
655 | cases and correctly check for parsing errors. | |
656 | ||
657 | - `htonl()`/`ntohl()` and `htons()`/`ntohs()` are weird. Please use `htobe32()` | |
658 | and `htobe16()` instead, it's much more descriptive, and actually says what | |
659 | really is happening, after all `htonl()` and `htons()` don't operate on | |
660 | `long`s and `short`s as their name would suggest, but on `uint32_t` and | |
661 | `uint16_t`. Also, "network byte order" is just a weird name for "big endian", | |
662 | hence we might want to call it "big endian" right-away. | |
663 | ||
a5b28b77 ZJS |
664 | - Use `typesafe_inet_ntop()`, `typesafe_inet_ntop4()`, and |
665 | `typesafe_inet_ntop6()` instead of `inet_ntop()`. But better yet, use the | |
666 | `IN_ADDR_TO_STRING()`, `IN4_ADDR_TO_STRING()`, and `IN6_ADDR_TO_STRING()` | |
74223cbe | 667 | macros which allocate an anonymous buffer internally. |
a5b28b77 | 668 | |
2d0dce2a | 669 | - Please never use `dup()`. Use `fcntl(fd, F_DUPFD_CLOEXEC, 3)` instead. For |
c1495f8e | 670 | two reasons: first, you want `O_CLOEXEC` set on the new `fd` (see |
2d0dce2a LP |
671 | above). Second, `dup()` will happily duplicate your `fd` as 0, 1, 2, |
672 | i.e. stdin, stdout, stderr, should those `fd`s be closed. Given the special | |
673 | semantics of those `fd`s, it's probably a good idea to avoid | |
674 | them. `F_DUPFD_CLOEXEC` with `3` as parameter avoids them. | |
675 | ||
82143987 FA |
676 | - Don't use `fgets()`, it's too hard to properly handle errors such as overly |
677 | long lines. Use `read_line()` instead, which is our own function that handles | |
c90b6abc | 678 | this much more nicely. |
2d0dce2a LP |
679 | |
680 | - Don't invoke `exit()`, ever. It is not replacement for proper error | |
681 | handling. Please escalate errors up your call chain, and use normal `return` | |
682 | to exit from the main function of a process. If you `fork()`ed off a child | |
683 | process, please use `_exit()` instead of `exit()`, so that the exit handlers | |
684 | are not run. | |
685 | ||
e109541f LP |
686 | - Do not use `basename()` or `dirname()`. The semantics in corner cases are |
687 | full of pitfalls, and the fact that there are two quite different versions of | |
688 | `basename()` (one POSIX and one GNU, of which the latter is much more useful) | |
689 | doesn't make it bette either. Use path_extract_filename() and | |
690 | path_extract_directory() instead. | |
831781b9 | 691 | |
bcef0f33 ZJS |
692 | - Never use `FILENAME_MAX`. Use `PATH_MAX` instead (for checking maximum size |
693 | of paths) and `NAME_MAX` (for checking maximum size of filenames). | |
694 | `FILENAME_MAX` is not POSIX, and is a confusingly named alias for `PATH_MAX` | |
6ae11e12 | 695 | on Linux. Note that `NAME_MAX` does not include space for a trailing `NUL`, |
bcef0f33 | 696 | but `PATH_MAX` does. UNIX FTW! |
b775b182 | 697 | |
ff2c2d08 | 698 | ## Committing to git |
831781b9 LP |
699 | |
700 | - Commit message subject lines should be prefixed with an appropriate component | |
701 | name of some kind. For example "journal: ", "nspawn: " and so on. | |
702 | ||
703 | - Do not use "Signed-Off-By:" in your commit messages. That's a kernel thing we | |
704 | don't do in the systemd project. | |
e8a587dc LP |
705 | |
706 | # Commenting | |
707 | ||
708 | - The best place for code comments and explanations is in the code itself. Only | |
709 | the second best is in git commit messages. The worst place is in the GitHub | |
710 | PR cover letter. Hence, whenever you type a commit message consider for a | |
711 | moment if what you are typing there wouldn't be a better fit for an in-code | |
712 | comment. And if you type the cover letter of a PR, think hard if this | |
713 | wouldn't be better as a commit message or even code comment. Comments are | |
714 | supposed to be useful for somebody who reviews the code, and hence hiding | |
715 | comments in git commits or PR cover letters makes reviews unnecessarily | |
716 | hard. Moreover, while we rely heavily on GitHub's project management | |
717 | infrastructure we'd like to keep everything that can reasonably be kept in | |
718 | the git repository itself in the git repository, so that we can theoretically | |
719 | move things elswhere with the least effort possible. | |
720 | ||
721 | - It's OK to reference GitHub PRs, GitHub issues and git commits from code | |
722 | comments. Cross-referencing code, issues, and documentation is a good thing. | |
723 | ||
724 | - Reasonable use of non-ASCII Unicode UTF-8 characters in code comments is | |
725 | welcome. If your code comment contains an emoji or two this will certainly | |
726 | brighten the day of the occasional reviewer of your code. Really! 😊 |