mirror of
https://github.com/systemd/systemd-stable.git
synced 2025-02-02 09:47:03 +03:00
sd-bus: bus_message_type_from_string is not pure
GCC document [1] says: The pure attribute prohibits a function from modifying the state of the program that is observable by means other than inspecting the function’s return value. And there is an example: `int hash (char *) __attribute__ ((pure));` ... Even though hash takes a non-const pointer argument it must not modify the array it points to, ... But we are modifying the object pointed to by the pointer u, which is clearly a violation of the semantic of pure. With -ftrivial-auto-var-init (enabled by -Dmode=release), on some targets (GCC 12.2 on AArch64 and GCC 13.1 on x86_64) performs an optimization: as the variable "u" in bus_match_parse has been zero-initialized (by the -ftrivial-auto-var-init option) and never modified (because a "pure" bus_message_type_from_string is not allowed to modify it), "u" will be always 0. Then 0 is used to initialize .value_u8 field of struct bus_match_component. This then causes a infinite event loop, so "systemctl restart" never stops, and pam_systemd timeouts communicating with logind, etc. So we should remove the "pure" attribute here. Fixes #26395. [1]:https://gcc.gnu.org/onlinedocs/gcc/Common-Function-Attributes.html#index-pure-function-attribute (cherry picked from commit 6723c28f36ea566faf61d3610012cd89f95ee4a0)
This commit is contained in:
parent
133d4ff6d6
commit
59dccdfddb
@ -361,7 +361,7 @@ bool path_complex_pattern(const char *pattern, const char *value) _pure_;
|
||||
bool namespace_simple_pattern(const char *pattern, const char *value) _pure_;
|
||||
bool path_simple_pattern(const char *pattern, const char *value) _pure_;
|
||||
|
||||
int bus_message_type_from_string(const char *s, uint8_t *u) _pure_;
|
||||
int bus_message_type_from_string(const char *s, uint8_t *u);
|
||||
const char *bus_message_type_to_string(uint8_t u) _pure_;
|
||||
|
||||
#define error_name_is_valid interface_name_is_valid
|
||||
|
Loading…
x
Reference in New Issue
Block a user