From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ua0-f200.google.com (mail-ua0-f200.google.com [209.85.217.200]) by kanga.kvack.org (Postfix) with ESMTP id EADE06B000C for ; Mon, 25 Jun 2018 12:25:10 -0400 (EDT) Received: by mail-ua0-f200.google.com with SMTP id j9-v6so4207016uan.8 for ; Mon, 25 Jun 2018 09:25:10 -0700 (PDT) Received: from mail-sor-f65.google.com (mail-sor-f65.google.com. [209.85.220.65]) by mx.google.com with SMTPS id l186-v6sor2167716vkh.120.2018.06.25.09.25.09 for (Google Transport Security); Mon, 25 Jun 2018 09:25:10 -0700 (PDT) MIME-Version: 1.0 References: <20180625160040.di75264empbcf6xz@lakrids.cambridge.arm.com> In-Reply-To: <20180625160040.di75264empbcf6xz@lakrids.cambridge.arm.com> From: Alexander Potapenko Date: Mon, 25 Jun 2018 18:24:57 +0200 Message-ID: Subject: Re: Calling vmalloc_to_page() on ioremap memory? Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Sender: owner-linux-mm@kvack.org List-ID: To: Mark Rutland Cc: Ard Biesheuvel , Andrew Morton , Linux Memory Management List On Mon, Jun 25, 2018 at 6:00 PM Mark Rutland wrote: > > On Mon, Jun 25, 2018 at 04:59:23PM +0200, Alexander Potapenko wrote: > > Hi Ard, Mark, Andrew and others, > > > > AFAIU, commit 029c54b09599573015a5c18dbe59cbdf42742237 ("mm/vmalloc.c: > > huge-vmap: fail gracefully on unexpected huge vmap mappings") was > > supposed to make vmalloc_to_page() return NULL for pointers not > > returned by vmalloc(). > > It's a little more subtle than that -- avoiding an edge case where we > unexpectedly hit huge mappings, rather than determining whether an > address same from vmalloc(). Ok, but anyway, acpi_os_ioremap() creates a huge page mapping via __ioremap_caller() (see https://elixir.bootlin.com/linux/latest/source/arch/x86/mm/ioremap.c#L133) Shouldn't these checks detect that as well? > > For memory error detection purposes I'm trying to map the addresses > > from the vmalloc range to valid struct pages, or at least make sure > > there's no struct page for a given address. > > Looking up the vmap_area_root rbtree isn't an option, as this must be > > done from instrumented code, including interrupt handlers. > > I'm not sure how you can do this without looking at VMAs. > > In general, the vmalloc area can contain addresses which are not memory, > and this cannot be detremined from the address alone. I thought this was exactly what vmalloc_to_page() did, but apparently no. > You *might* be able to get away with pfn_valid(vmalloc_to_pfn(x)), but > IIRC there's some disagreement on the precise meaning of pfn_valid(), so > that might just tell you that the address happens to fall close to some > valid memory. This appears to work, at least for ACPI mappings. I'll check other cases th= ough. Thank you! > Thanks, > Mark. --=20 Alexander Potapenko Software Engineer Google Germany GmbH Erika-Mann-Stra=C3=9Fe, 33 80636 M=C3=BCnchen Gesch=C3=A4ftsf=C3=BChrer: Paul Manicle, Halimah DeLaine Prado Registergericht und -nummer: Hamburg, HRB 86891 Sitz der Gesellschaft: Hamburg