linux-kernel - Re: [PATCH] rtc: allow rtc_read_alarm without read

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <1c631d431d134f78d72bb3c23bb692f62d67803a.camel@toradex.com>
Date:   Wed, 15 Feb 2023 15:00:43 +0000
From:   Philippe Schenker <philippe.schenker@...adex.com>
To:     "a.zummo@...ertech.it" <a.zummo@...ertech.it>,
        "alexandre.belloni@...tlin.com" <alexandre.belloni@...tlin.com>
CC:     Marcel Ziswiler <marcel.ziswiler@...adex.com>,
        "zhipeng.wang_1@....com" <zhipeng.wang_1@....com>,
        "linux-rtc@...r.kernel.org" <linux-rtc@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Francesco Dolcini <francesco.dolcini@...adex.com>
Subject: Re: [PATCH] rtc: allow rtc_read_alarm without read_alarm callback

On Tue, 2023-02-14 at 23:27 +0100, alexandre.belloni@...tlin.com wrote:
> From: Alexandre Belloni <alexandre.belloni@...tlin.com>
> 
> .read_alarm is not necessary to read the current alarm because it is
> recorded in the aie_timer and so rtc_read_alarm() will never call
> rtc_read_alarm_internal() which is the only function calling the
> callback.
> 
> Reported-by: Zhipeng Wang <zhipeng.wang_1@....com>
> Reported-by: Marcel Ziswiler <marcel.ziswiler@...adex.com>
> Fixes: 7ae41220ef58 ("rtc: introduce features bitfield")
> Signed-off-by: Alexandre Belloni <alexandre.belloni@...tlin.com>

Tested-by: Philippe Schenker <philippe.schenker@...adex.com>

I tested on our SoMs Colibri iMX8X and Apalis iMX8

I used the variants that had i.MX 8QXP and i.MX 8QM placed. This patch
did solve the problem we currently have. I also wanted to mention that I
could not get them to run on a mainline kernel in a acceptable time-
frame so I tested on Toradex's kernel that is based on NXP's Kernel. [1]

[1]
https://git.toradex.com/cgit/linux-toradex.git/log/?h=toradex_5.15-2.1.x-imx

> ---
>  drivers/rtc/interface.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/rtc/interface.c b/drivers/rtc/interface.c
> index 7c30cb3c764d..499d89150afc 100644
> --- a/drivers/rtc/interface.c
> +++ b/drivers/rtc/interface.c
> @@ -392,7 +392,7 @@ int rtc_read_alarm(struct rtc_device *rtc, struct
> rtc_wkalrm *alarm)
>                 return err;
>         if (!rtc->ops) {
>                 err = -ENODEV;
> -       } else if (!test_bit(RTC_FEATURE_ALARM, rtc->features) ||
> !rtc->ops->read_alarm) {
> +       } else if (!test_bit(RTC_FEATURE_ALARM, rtc->features)) {
>                 err = -EINVAL;
>         } else {
>                 memset(alarm, 0, sizeof(struct rtc_wkalrm));