linux-kernel - Re: [PATCH] Staging: fbtft: Fix iomem dereference

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: <CAAm8cU6B_JTYPt0urTLzq1T78DcaLuR1=23PhZYrPV59SAOGyw@mail.gmail.com>
Date:	Tue, 18 Aug 2015 19:08:09 +0530
From:	Ronit Halder <ronit.crj@...il.com>
To:	Dan Carpenter <dan.carpenter@...cle.com>
Subject: Re: [PATCH] Staging: fbtft: Fix iomem dereference

Yes, it is not I/O memory address. I was wrong on that.
But it makes sparse happy.
Is here any side effect of using ioread16() ?

regards,
ronit

On Tue, Aug 18, 2015 at 2:27 PM, Dan Carpenter <dan.carpenter@...cle.com> wrote:
> On Tue, Aug 18, 2015 at 12:16:57PM +0530, Ronit Halder wrote:
>> This patch fixes the warning generated by sparse
>> "cast removes address space of expression" by using ioread16
>> function insted of directly dereferencing I/O memory.
>>
>> Signed-off-by: Ronit halder <ronit.crj@...il.com>
>
> Are these really iomem pointers?  A lot of drivers use a fake
> screen_base which is just a buffer of normal memory.
>
> regards,
> dan carpenter
>

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/