Commit 877e9119 authored by Nathan Chancellor's avatar Nathan Chancellor Committed by Lee Jones

leds: leds-mt6323: Adjust return/parameter types in wled get/set callbacks

Clang's kernel Control Flow Integrity (kCFI) is a compiler-based
security mitigation that ensures the target of an indirect function call
matches the expected type of the call and trapping if they do not match
exactly. The warning -Wincompatible-function-pointer-types-strict aims
to catch these issues at compile time, which reveals:

 drivers/leds/leds-mt6323.c:598:49: error: incompatible function pointer types assigning to 'int (*)(struct led_classdev *, enum led_brightness)' from 'int (struct led_classdev *, unsigned int)' [-Werror,-Wincompatible-function-pointer-types-strict]
   598 |                         leds->led[reg]->cdev.brightness_set_blocking =
       |                                                                      ^
   599 |                                                 mt6323_wled_set_brightness;
       |                                                 ~~~~~~~~~~~~~~~~~~~~~~~~~~
 drivers/leds/leds-mt6323.c:600:40: error: incompatible function pointer types assigning to 'enum led_brightness (*)(struct led_classdev *)' from 'unsigned int (struct led_classdev *)' [-Werror,-Wincompatible-function-pointer-types-strict]
   600 |                         leds->led[reg]->cdev.brightness_get =
       |                                                             ^
   601 |                                                 mt6323_get_wled_brightness;
       |                                                 ~~~~~~~~~~~~~~~~~~~~~~~~~~
 2 errors generated.

While 'unsigned int' is ABI compatible with 'enum led_brightness' (hence
no warning from -Wincompatible-function-pointer-types) and the callers
of these callbacks use/pass the values as 'unsigned int', the mismatch
between the prototype and the called function will trip kCFI at runtime.

Change the types in the implementations to match the prototypes, clearing
up the warning and avoiding kCFI failures.

Fixes: 9bb0a9e0 ("leds: leds-mt6323: Add support for WLEDs and MT6332")
Signed-off-by: default avatarNathan Chancellor <nathan@kernel.org>
Reviewed-by: default avatarNick Desaulniers <ndesaulniers@google.com>
Reviewed-by: default avatarAngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
Link: https://lore.kernel.org/r/20230622-mt6323-wled-wincompatible-function-pointer-types-strict-v1-1-6ad256f220e8@kernel.orgSigned-off-by: default avatarLee Jones <lee@kernel.org>
parent 7bd932d9
...@@ -76,7 +76,7 @@ struct mt6323_led { ...@@ -76,7 +76,7 @@ struct mt6323_led {
int id; int id;
struct mt6323_leds *parent; struct mt6323_leds *parent;
struct led_classdev cdev; struct led_classdev cdev;
unsigned int current_brightness; enum led_brightness current_brightness;
}; };
/** /**
...@@ -451,7 +451,7 @@ static int mtk_wled_hw_off(struct led_classdev *cdev) ...@@ -451,7 +451,7 @@ static int mtk_wled_hw_off(struct led_classdev *cdev)
return 0; return 0;
} }
static unsigned int mt6323_get_wled_brightness(struct led_classdev *cdev) static enum led_brightness mt6323_get_wled_brightness(struct led_classdev *cdev)
{ {
struct mt6323_led *led = container_of(cdev, struct mt6323_led, cdev); struct mt6323_led *led = container_of(cdev, struct mt6323_led, cdev);
struct mt6323_leds *leds = led->parent; struct mt6323_leds *leds = led->parent;
...@@ -471,7 +471,7 @@ static unsigned int mt6323_get_wled_brightness(struct led_classdev *cdev) ...@@ -471,7 +471,7 @@ static unsigned int mt6323_get_wled_brightness(struct led_classdev *cdev)
} }
static int mt6323_wled_set_brightness(struct led_classdev *cdev, static int mt6323_wled_set_brightness(struct led_classdev *cdev,
unsigned int brightness) enum led_brightness brightness)
{ {
struct mt6323_led *led = container_of(cdev, struct mt6323_led, cdev); struct mt6323_led *led = container_of(cdev, struct mt6323_led, cdev);
struct mt6323_leds *leds = led->parent; struct mt6323_leds *leds = led->parent;
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment