linux-kernel - Re: drivers/mtd/maps/physmap-bt1-rom.c:78:18: sparse: sparse: cast removes address space '_

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]

Date:   Tue, 10 Nov 2020 16:35:56 +0100
From:   Miquel Raynal <miquel.raynal@...tlin.com>
To:     Serge Semin <Sergey.Semin@...kalelectronics.ru>
Cc:     kernel test robot <lkp@...el.com>, <kbuild-all@...ts.01.org>,
        <linux-kernel@...r.kernel.org>, <linux-mtd@...ts.infradead.org>
Subject: Re: drivers/mtd/maps/physmap-bt1-rom.c:78:18: sparse: sparse: cast
 removes address space '__iomem' of expression

Hi Serge,

Serge Semin <Sergey.Semin@...kalelectronics.ru> wrote on Tue, 10 Nov
2020 14:38:27 +0300:

> Hello Miquel,
> 
> A situation noted by the warning below won't cause any problem because
> the casting is done to a non-dereferenced variable. It is utilized
> as a pointer bias later in that function. Shall we just ignore the
> warning or still fix it somehow?

Do you think the cast to a !__iomem value is mandatory here?

Perhaps if you find an elegant wait to avoid the warning it would be
nice, otherwise I guess we'll let it aside as a false positive.

Cheers,
Miquèl