linux-kernel - Re: [PATCH v3 1/2] staging: slicoss: fix different address space warnings: 32 bits

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: <20161117113302.GU28558@mwanda>
Date:   Thu, 17 Nov 2016 14:33:02 +0300
From:   Dan Carpenter <dan.carpenter@...cle.com>
To:     Sergio Paracuellos <sergio.paracuellos@...il.com>
Cc:     Greg KH <gregkh@...uxfoundation.org>, devel@...verdev.osuosl.org,
        linux-kernel <linux-kernel@...r.kernel.org>,
        Lior Dotan <liodot@...il.com>
Subject: Re: [PATCH v3 1/2] staging: slicoss: fix different address space
 warnings: 32 bits

On Thu, Nov 17, 2016 at 12:22:00PM +0100, Sergio Paracuellos wrote:
> On Thu, Nov 17, 2016 at 11:51 AM, Dan Carpenter
> <dan.carpenter@...cle.com> wrote:
> > Hm...  I seem to duplicate the Sparse warnings at all.  That's weird.
> >
> 
> With this patch applied, sparse warnings dissapear for me... That's weird.
>

I understand that.

> > Anyway as far as I can tell the warnings are false positives...  Can't
> > you just remove the __iomem tag?  Have you tested this change?
> >
> I haven' t tested this change because I can't test it :(. Do you think
> that just removing
> __iomem tag is enough?

Give it a shot and see if the warnings go away.  I don't think the tag
is correct.

regards,
dan carpenter