From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.3 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id B058AC432BE for ; Fri, 27 Aug 2021 17:10:46 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 9805060E93 for ; Fri, 27 Aug 2021 17:10:46 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236514AbhH0RLe (ORCPT ); Fri, 27 Aug 2021 13:11:34 -0400 Received: from verein.lst.de ([213.95.11.211]:34663 "EHLO verein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234297AbhH0RLd (ORCPT ); Fri, 27 Aug 2021 13:11:33 -0400 Received: by verein.lst.de (Postfix, from userid 2407) id 0EE4967373; Fri, 27 Aug 2021 19:10:42 +0200 (CEST) Date: Fri, 27 Aug 2021 19:10:41 +0200 From: Christoph Hellwig To: Linus Torvalds Cc: Christoph Hellwig , Will Deacon , Catalin Marinas , Linux ARM , Linux Kernel Mailing List , Android Kernel Team Subject: Re: [GIT PULL] arm64 fix for 5.14 Message-ID: <20210827171041.GA28149@lst.de> References: <20210826131747.GE26318@willie-the-truck> <20210827074041.GA24309@lst.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Aug 27, 2021 at 10:03:29AM -0700, Linus Torvalds wrote: > The ARM code actually uses that complex pfn_to_section_nr() and > memblock_is_memory() etc. That seems a bit of an overkill, since the > memblock code should have translated all that into being reserved. > > But again, I don't actually know exactly what triggered the issue on > ARM, so the above is just my "this seems to be a more proper check" > suggestion. They CCed me on their earlier discussion, but I did not catch up on it until you responded to the pull request If I understood it correct it was about a platform device mapping a MMIO region (like a PCI bar), but something about section alignment cause pfn_valid to mistrigger.