linux-kernel - Re: [v9,4/5] watchdog: Add RAVE SP watchdog driver

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: <CAHQ1cqG=ceHLE-2DwrtL90BUDHbbH9bCma06-LO2SSuqZkX99A@mail.gmail.com>
Date:   Tue, 31 Oct 2017 08:41:28 -0700
From:   Andrey Smirnov <andrew.smirnov@...il.com>
To:     Guenter Roeck <linux@...ck-us.net>
Cc:     linux-kernel <linux-kernel@...r.kernel.org>,
        linux-watchdog@...r.kernel.org, Chris Healy <cphealy@...il.com>,
        Lucas Stach <l.stach@...gutronix.de>,
        Nikita Yushchenko <nikita.yoush@...entembedded.com>,
        Lee Jones <lee.jones@...aro.org>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Pavel Machek <pavel@....cz>,
        Andy Shevchenko <andy.shevchenko@...il.com>,
        Rob Herring <robh@...nel.org>, Johan Hovold <johan@...nel.org>
Subject: Re: [v9,4/5] watchdog: Add RAVE SP watchdog driver

On Sat, Oct 28, 2017 at 9:14 AM, Guenter Roeck <linux@...ck-us.net> wrote:
> On Wed, Oct 25, 2017 at 12:04:20PM -0700, Andrey Smirnov wrote:
>> This driver provides access to RAVE SP watchdog functionality.
>>
>> Cc: linux-kernel@...r.kernel.org
>> Cc: linux-watchdog@...r.kernel.org
>> Cc: cphealy@...il.com
>> Cc: Lucas Stach <l.stach@...gutronix.de>
>> Cc: Nikita Yushchenko <nikita.yoush@...entembedded.com>
>> Cc: Lee Jones <lee.jones@...aro.org>
>> Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
>> Cc: Pavel Machek <pavel@....cz>
>> Cc: Andy Shevchenko <andy.shevchenko@...il.com>
>> Cc: Guenter Roeck <linux@...ck-us.net>
>> Cc: Rob Herring <robh@...nel.org>
>> Cc: Johan Hovold <johan@...nel.org>
>> Signed-off-by: Nikita Yushchenko <nikita.yoush@...entembedded.com>
>> Signed-off-by: Andrey Smirnov <andrew.smirnov@...il.com>
>> ---
>>
>> Guenter:
>>
>> In our previous discussion you noted that relying on the state of
>> WDOG_HW_RUNNING was not correct (that should be fixed now), please let
>> me know if using watchdog_hw_running() the way I do in
>> rave_sp_wdt_set_timeout() is incorrect as well.
>>
>
> You could as well have used watchdog_active(), but it is ok.
>

That's easy to change. I'll do that in v10.


>> Thanks,
>> Andrey Smirnov
>>
>>  drivers/watchdog/Kconfig       |   7 +
>>  drivers/watchdog/Makefile      |   1 +
>>  drivers/watchdog/rave-sp-wdt.c | 343 +++++++++++++++++++++++++++++++++++++++++
>>  3 files changed, 351 insertions(+)
>>  create mode 100644 drivers/watchdog/rave-sp-wdt.c
>>
> [ ... ]
>
>> +
>> +static int rave_sp_wdt_probe(struct platform_device *pdev)
>> +{
>> +     struct device *dev = &pdev->dev;
>> +     const struct of_device_id *id;
>> +     struct watchdog_device *wdd;
>> +     struct rave_sp_wdt *sp_wd;
>> +     struct nvmem_cell *cell;
>> +     __le16 timeout = 0;
>> +     int ret;
>> +
>> +     id = of_match_device(rave_sp_wdt_variants, dev->parent);
>> +     if (WARN_ON(!id))
>> +             return -ENODEV;
>> +
>
> I could understand an error message here, but why a traceback ?
>

I can't think of a good reason for it. I'll change this to a regular
error message in v10.

Thanks,
Andrey Smirnov