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: <CAMhs-H9jqA2k19ZAPQJTuAC77bdOXFs6gindFFJOBAtELARoFw@mail.gmail.com>
Date:   Thu, 17 Nov 2016 12:46:12 +0100
From:   Sergio Paracuellos <sergio.paracuellos@...il.com>
To:     Dan Carpenter <dan.carpenter@...cle.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:33 PM, Dan Carpenter
<dan.carpenter@...cle.com> wrote:
> Give it a shot and see if the warnings go away.  I don't think the tag
> is correct.

Just removing __iomem tag in shmem_data field of slic_shmemory struct
makes sparse happy. No warnings around.

Should I send a v4 patch with the tag removed?

Cheers,
    Sergio Paracuellos