Received: by 2002:ac0:946b:0:0:0:0:0 with SMTP id j40csp1227182imj; Sun, 17 Feb 2019 00:43:20 -0800 (PST) X-Google-Smtp-Source: AHgI3IaUhBOz5iqDKJQ/iQKk7vLbUyEdg3buyjyTC/XrxskE1aKTw4H1/lVkVk8qkQvsHQ4kz9qw X-Received: by 2002:a63:b04:: with SMTP id 4mr12910656pgl.365.1550393000364; Sun, 17 Feb 2019 00:43:20 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1550393000; cv=none; d=google.com; s=arc-20160816; b=OK9upySvSiBIIZ6AVYhSk2cLsbIG6JQk+V/JgczmldpCf0mVJGR6ekwIHPd/tr4ZVM rlSHT6Udv+JscbKZpJcdylK4gvvzLnNW/cbaKFiORj6gT7qUcbCJoUvkki+R1hNAMPD4 f+CMdaweqim3c05n5j3sTsIC1Nwt/Zpee+tq8D/QzwndakLVgoKBrPfmIo8JmWA2Nmjx g8amHQWU1AD2MnM46NGmcVEBuGcyD2oKw34i6gMGh2H1rhr5GxsOwaZCbSojvCSW3NDW lXBr5B2Gq3agVHGoWuo9uYTWvuMGNK/8Lfx5rTo0JD9RBWuy5q0NZkL3B8nujFeC/kIx LKNQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:message-id:date:references :in-reply-to:subject:cc:to:from; bh=X6V94a/BrXX5nh4fCozOBtzpMFCIqnvf0UfEvRAcQdQ=; b=UKpSkrXZ14tWXa5u6wvcGbSNp/LvAOM48TG0jFsKBdcxvzGnKa292q4n7ufbRnQEsW W0mbZ2GtectIBHcTAEsPSFjuT+X44I4tBluEyb/HBDSsr/WJOYBv7urfxmjivsfoI3a6 bpmaRF5/EF2k4U29gOYkgqallZkznXXI4LDUsoOylQfmZvYuL2gyHihupfSE2M3w7fqs v7uwbBd8v3YYooUgwhcqOjqdwrRsKgUI2XsJPfWZYi9giKCMO+09A+s59I7pixYQueVO HpzSSTjnxNRkBpjWBCRp3ByxG+bWeYqvhp1ATXikVQnUg9jYuGcuZD5AZAgC+YoA6SNw SQZw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id f13si5306531pgq.355.2019.02.17.00.43.04; Sun, 17 Feb 2019 00:43:20 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726370AbfBQIej (ORCPT + 99 others); Sun, 17 Feb 2019 03:34:39 -0500 Received: from ozlabs.org ([203.11.71.1]:40759 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725768AbfBQIej (ORCPT ); Sun, 17 Feb 2019 03:34:39 -0500 Received: from authenticated.ozlabs.org (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ozlabs.org (Postfix) with ESMTPSA id 442Kzx30D5z9sLw; Sun, 17 Feb 2019 19:34:37 +1100 (AEDT) From: Michael Ellerman To: Segher Boessenkool , Balbir Singh Cc: erhard_f@mailbox.org, jack@suse.cz, linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, aneesh.kumar@linux.vnet.ibm.com Subject: Re: [PATCH] powerpc/64s: Fix possible corruption on big endian due to pgd/pud_present() In-Reply-To: <20190216142206.GE14180@gate.crashing.org> References: <20190214062339.7139-1-mpe@ellerman.id.au> <20190216105511.GA31125@350D> <20190216142206.GE14180@gate.crashing.org> Date: Sun, 17 Feb 2019 19:34:36 +1100 Message-ID: <87bm3add9f.fsf@concordia.ellerman.id.au> MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Segher Boessenkool writes: > Hi all, > > On Sat, Feb 16, 2019 at 09:55:11PM +1100, Balbir Singh wrote: >> On Thu, Feb 14, 2019 at 05:23:39PM +1100, Michael Ellerman wrote: >> > In v4.20 we changed our pgd/pud_present() to check for _PAGE_PRESENT >> > rather than just checking that the value is non-zero, e.g.: >> > >> > static inline int pgd_present(pgd_t pgd) >> > { >> > - return !pgd_none(pgd); >> > + return (pgd_raw(pgd) & cpu_to_be64(_PAGE_PRESENT)); >> > } >> > >> > Unfortunately this is broken on big endian, as the result of the >> > bitwise && is truncated to int, which is always zero because > > (Bitwise "&" of course). Thanks, I fixed that up. cheers