linux-kernel - Re: [PATCH] nvmem: core: fix nvmem_cell

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAK8P3a0rqeksffu4swv2BGzhd68Brb76VFUCyfqtFAu6QppVgA@mail.gmail.com>
Date:   Tue, 17 Sep 2019 09:57:16 +0200
From:   Arnd Bergmann <arnd@...db.de>
To:     Sebastian Reichel <sre@...nel.org>
Cc:     Srinivas Kandagatla <srinivas.kandagatla@...aro.org>,
        Sebastian Reichel <sebastian.reichel@...labora.com>,
        kbuild test robot <lkp@...el.com>,
        Han Nandor <nandor.han@...sala.com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] nvmem: core: fix nvmem_cell_write inline function

On Mon, Sep 9, 2019 at 3:45 PM Sebastian Reichel <sre@...nel.org> wrote:
>
> From: Sebastian Reichel <sebastian.reichel@...labora.com>
>
> nvmem_cell_write's buf argument uses different types based on
> the configuration of CONFIG_NVMEM. The function prototype for
> enabled NVMEM uses 'void *' type, but the static dummy function
> for disabled NVMEM uses 'const char *' instead. Fix the different
> behaviour by always expecting a 'void *' typed buf argument.
>
> Fixes: 7a78a7f7695b ("power: reset: nvmem-reboot-mode: use NVMEM as reboot mode write interface")
> Reported-by: kbuild test robot <lkp@...el.com>
> Cc: Han Nandor <nandor.han@...sala.com>
> Cc: Srinivas Kandagatla <srinivas.kandagatla@...aro.org>
> Cc: linux-kernel@...r.kernel.org
> Signed-off-by: Sebastian Reichel <sebastian.reichel@...labora.com>

I still see the issue in linux-next, did this get dropped by accident?

      Arnd