Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH] mm: riscv: fix an unsafe pte read in huge_pte_alloc()
From:   patchwork-bot+linux-riscv@kernel.org
Message-Id: <168860102266.23922.10126828574164842204.git-patchwork-notify@kernel.org>
Date:   Wed, 05 Jul 2023 23:50:22 +0000
References: <20230703190044.311730-1-jhubbard@nvidia.com>
In-Reply-To: <20230703190044.311730-1-jhubbard@nvidia.com>
To:     John Hubbard <jhubbard@nvidia.com>
Cc:     linux-riscv@lists.infradead.org, akpm@linux-foundation.org,
        aou@eecs.berkeley.edu, alexghiti@rivosinc.com,
        ajones@ventanamicro.com, hughd@google.com, palmer@dabbelt.com,
        paul.walmsley@sifive.com, panqinglin2020@iscas.ac.cn,
        linux-mm@kvack.org, linux-kernel@vger.kernel.org,
        jthoughton@google.com, ryan.roberts@arm.com
Precedence: bulk

Hello:

This patch was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:

On Mon, 3 Jul 2023 12:00:44 -0700 you wrote:
> The WARN_ON_ONCE() statement in riscv's huge_pte_alloc() is susceptible
> to false positives, because the pte is read twice at the C language
> level, locklessly, within the same conditional statement. Depending on
> compiler behavior, this can lead to generated machine code that actually
> reads the pte just once, or twice. Reading twice will expose the code to
> changing pte values and cause incorrect behavior.
> 
> [...]

Here is the summary with links:
  - mm: riscv: fix an unsafe pte read in huge_pte_alloc()
    https://git.kernel.org/riscv/c/62ba41d27612

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html