diff options
author | Christophe JAILLET <christophe.jaillet@wanadoo.fr> | 2023-09-23 10:15:38 +0300 |
---|---|---|
committer | Lee Jones <lee@kernel.org> | 2023-11-01 14:28:51 +0300 |
commit | ff50f53276131a3059e8307d11293af388ed2bcd (patch) | |
tree | 76c8d34a0388d9464dd7e8868eea36051d73dbbe /drivers/watchdog/bcm2835_wdt.c | |
parent | 76fe464c8e64e71b2e4af11edeef0e5d85eeb6aa (diff) | |
download | linux-ff50f53276131a3059e8307d11293af388ed2bcd.tar.xz |
leds: trigger: ledtrig-cpu:: Fix 'output may be truncated' issue for 'cpu'
In order to teach the compiler that 'trig->name' will never be truncated,
we need to tell it that 'cpu' is not negative.
When building with W=1, this fixes the following warnings:
drivers/leds/trigger/ledtrig-cpu.c: In function ‘ledtrig_cpu_init’:
drivers/leds/trigger/ledtrig-cpu.c:155:56: error: ‘%d’ directive output may be truncated writing between 1 and 11 bytes into a region of size 5 [-Werror=format-truncation=]
155 | snprintf(trig->name, MAX_NAME_LEN, "cpu%d", cpu);
| ^~
drivers/leds/trigger/ledtrig-cpu.c:155:52: note: directive argument in the range [-2147483648, 7]
155 | snprintf(trig->name, MAX_NAME_LEN, "cpu%d", cpu);
| ^~~~~~~
drivers/leds/trigger/ledtrig-cpu.c:155:17: note: ‘snprintf’ output between 5 and 15 bytes into a destination of size 8
155 | snprintf(trig->name, MAX_NAME_LEN, "cpu%d", cpu);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Fixes: 8f88731d052d ("led-triggers: create a trigger for CPU activity")
Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Link: https://lore.kernel.org/r/3f4be7a99933cf8566e630da54f6ab913caac432.1695453322.git.christophe.jaillet@wanadoo.fr
Signed-off-by: Lee Jones <lee@kernel.org>
Diffstat (limited to 'drivers/watchdog/bcm2835_wdt.c')
0 files changed, 0 insertions, 0 deletions