linux-kernel - Re: [Xen-devel] [PATCH 3/8] drm/xen-front: fix 32-bit build warning

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, 29 May 2018 09:59:46 +0200
From:   Arnd Bergmann <arnd@...db.de>
To:     Oleksandr Andrushchenko <andr2000@...il.com>
Cc:     Oleksandr Andrushchenko <oleksandr_andrushchenko@...m.com>,
        David Airlie <airlied@...ux.ie>,
        Daniel Vetter <daniel.vetter@...ll.ch>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        dri-devel <dri-devel@...ts.freedesktop.org>,
        xen-devel@...ts.xen.org,
        Boris Ostrovsky <boris.ostrovsky@...cle.com>,
        Dan Carpenter <dan.carpenter@...cle.com>
Subject: Re: [Xen-devel] [PATCH 3/8] drm/xen-front: fix 32-bit build warning

On Tue, May 29, 2018 at 7:58 AM, Oleksandr Andrushchenko
<andr2000@...il.com> wrote:
> On 05/25/2018 06:50 PM, Arnd Bergmann wrote:

>> b/drivers/gpu/drm/xen/xen_drm_front_shbuf.c
>> index 8099cb343ae3..d333b67cc1a0 100644
>> --- a/drivers/gpu/drm/xen/xen_drm_front_shbuf.c
>> +++ b/drivers/gpu/drm/xen/xen_drm_front_shbuf.c
>> @@ -122,7 +122,7 @@ static void guest_calc_num_grefs(struct
>> xen_drm_front_shbuf *buf)
>>   }
>>     #define xen_page_to_vaddr(page) \
>> -               ((phys_addr_t)pfn_to_kaddr(page_to_xen_pfn(page)))
>> +               ((uintptr_t)pfn_to_kaddr(page_to_xen_pfn(page)))
>>     static int backend_unmap(struct xen_drm_front_shbuf *buf)
>>   {
>
> Thank you for your patch: this issue was already discussed [1] and applied
> [2] to
> drm-misc-next.

Ok, thanks, and sorry for the duplicate. Linux-next releases have been
a bit sporadic recently so I didn't run the latest tree for all cases.

    Arnd