* [PATCH] rtc: max77686: Properly handle regmap_irq_get_virq() error code
@ 2016-02-04 0:26 Krzysztof Kozlowski
2016-02-04 2:47 ` Javier Martinez Canillas
2016-02-04 22:49 ` Alexandre Belloni
0 siblings, 2 replies; 3+ messages in thread
From: Krzysztof Kozlowski @ 2016-02-04 0:26 UTC (permalink / raw)
To: Chanwoo Choi, Krzysztof Kozlowski, Alessandro Zummo,
Alexandre Belloni, linux-kernel, rtc-linux
Cc: ldewangan, javier
The regmap_irq_get_virq() can return 0 or -EINVAL in error conditions
but driver checked only for value of 0.
This could lead to a cast of -EINVAL to an unsigned int used as a
interrupt number for devm_request_threaded_irq(). Although this is not
yet fatal (devm_request_threaded_irq() will just fail with -EINVAL) but
might be a misleading when diagnosing errors.
Signed-off-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>
Fixes: 6f1c1e71d933 ("mfd: max77686: Convert to use regmap_irq")
---
Patch rebased on current mainline, not RTC tree, because IMHO it is
a candidate for current RC-cycle.
Not marking cc-stable because behavior is not fatal - unless there is
an interrupt with number 4294967274 (then it would be successfully
requested for RTC driver).
---
drivers/rtc/rtc-max77686.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/rtc/rtc-max77686.c b/drivers/rtc/rtc-max77686.c
index 7184a0eda793..725dccae24e7 100644
--- a/drivers/rtc/rtc-max77686.c
+++ b/drivers/rtc/rtc-max77686.c
@@ -465,7 +465,7 @@ static int max77686_rtc_probe(struct platform_device *pdev)
info->virq = regmap_irq_get_virq(max77686->rtc_irq_data,
MAX77686_RTCIRQ_RTCA1);
- if (!info->virq) {
+ if (info->virq <= 0) {
ret = -ENXIO;
goto err_rtc;
}
--
1.9.1
^ permalink raw reply related [flat|nested] 3+ messages in thread
* Re: [PATCH] rtc: max77686: Properly handle regmap_irq_get_virq() error code
2016-02-04 0:26 [PATCH] rtc: max77686: Properly handle regmap_irq_get_virq() error code Krzysztof Kozlowski
@ 2016-02-04 2:47 ` Javier Martinez Canillas
2016-02-04 22:49 ` Alexandre Belloni
1 sibling, 0 replies; 3+ messages in thread
From: Javier Martinez Canillas @ 2016-02-04 2:47 UTC (permalink / raw)
To: Krzysztof Kozlowski, Chanwoo Choi, Alessandro Zummo,
Alexandre Belloni, linux-kernel, rtc-linux
Cc: ldewangan
Hello Krzysztof,
On 02/03/2016 09:26 PM, Krzysztof Kozlowski wrote:
> The regmap_irq_get_virq() can return 0 or -EINVAL in error conditions
> but driver checked only for value of 0.
>
> This could lead to a cast of -EINVAL to an unsigned int used as a
> interrupt number for devm_request_threaded_irq(). Although this is not
> yet fatal (devm_request_threaded_irq() will just fail with -EINVAL) but
> might be a misleading when diagnosing errors.
>
> Signed-off-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>
> Fixes: 6f1c1e71d933 ("mfd: max77686: Convert to use regmap_irq")
>
> ---
>
Good catch.
Reviewed-by: Javier Martinez Canillas <javier@osg.samsung.com>
Best regards,
--
Javier Martinez Canillas
Open Source Group
Samsung Research America
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH] rtc: max77686: Properly handle regmap_irq_get_virq() error code
2016-02-04 0:26 [PATCH] rtc: max77686: Properly handle regmap_irq_get_virq() error code Krzysztof Kozlowski
2016-02-04 2:47 ` Javier Martinez Canillas
@ 2016-02-04 22:49 ` Alexandre Belloni
1 sibling, 0 replies; 3+ messages in thread
From: Alexandre Belloni @ 2016-02-04 22:49 UTC (permalink / raw)
To: Krzysztof Kozlowski
Cc: Chanwoo Choi, Alessandro Zummo, linux-kernel, rtc-linux,
ldewangan, javier
On 04/02/2016 at 09:26:35 +0900, Krzysztof Kozlowski wrote :
> The regmap_irq_get_virq() can return 0 or -EINVAL in error conditions
> but driver checked only for value of 0.
>
> This could lead to a cast of -EINVAL to an unsigned int used as a
> interrupt number for devm_request_threaded_irq(). Although this is not
> yet fatal (devm_request_threaded_irq() will just fail with -EINVAL) but
> might be a misleading when diagnosing errors.
>
> Signed-off-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>
> Fixes: 6f1c1e71d933 ("mfd: max77686: Convert to use regmap_irq")
>
> ---
>
> Patch rebased on current mainline, not RTC tree, because IMHO it is
> a candidate for current RC-cycle.
>
> Not marking cc-stable because behavior is not fatal - unless there is
> an interrupt with number 4294967274 (then it would be successfully
> requested for RTC driver).
> ---
> drivers/rtc/rtc-max77686.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
Applied, thanks.
--
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2016-02-04 22:49 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-02-04 0:26 [PATCH] rtc: max77686: Properly handle regmap_irq_get_virq() error code Krzysztof Kozlowski
2016-02-04 2:47 ` Javier Martinez Canillas
2016-02-04 22:49 ` Alexandre Belloni
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).