linux-kernel - Re: [tip: x86/urgent] x86/ioremap: Use is_ioremap

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: <875xrujkeu.ffs@tglx>
Date: Wed, 21 Aug 2024 11:27:05 +0200
From: Thomas Gleixner <tglx@...utronix.de>
To: Max R <max8rr8@...il.com>
Cc: tip-bot2 for Max Ramanouski <tip-bot2@...utronix.de>,
 linux-tip-commits@...r.kernel.org, Christoph Hellwig <hch@....de>,
 Alistair Popple <apopple@...dia.com>, x86@...nel.org,
 linux-kernel@...r.kernel.org
Subject: Re: [tip: x86/urgent] x86/ioremap: Use is_ioremap_addr() in iounmap()

On Wed, Aug 21 2024 at 11:35, Max R. wrote:

Please do not top-post and trim your replies.

> Apparently,  x86-32 doesn't provide VMALLOC_START in asm/pgtable.h,
> and after a quick glance it seems to be the only arch to do so...
> Probably the correct solution is to add include asm/vmalloc.h to
> include/linux/ioremap.h, considering it uses VMALLOC_START. Will
> resubmit the v4 version of patch later today.

Careful, this might end up with other issues vs. the kernel header
inclusion hell.

If i386 is the only one which does not have VMALLOC start in
asm/pgtable.h, then curing this might be the easier fix, no?

Thanks,

        tglx