[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <168860102266.23922.10126828574164842204.git-patchwork-notify@kernel.org>
Date: Wed, 05 Jul 2023 23:50:22 +0000
From: patchwork-bot+linux-riscv@...nel.org
To: John Hubbard <jhubbard@...dia.com>
Cc: linux-riscv@...ts.infradead.org, akpm@...ux-foundation.org,
aou@...s.berkeley.edu, alexghiti@...osinc.com,
ajones@...tanamicro.com, hughd@...gle.com, palmer@...belt.com,
paul.walmsley@...ive.com, panqinglin2020@...as.ac.cn,
linux-mm@...ck.org, linux-kernel@...r.kernel.org,
jthoughton@...gle.com, ryan.roberts@....com
Subject: Re: [PATCH] mm: riscv: fix an unsafe pte read in huge_pte_alloc()
Hello:
This patch was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@...osinc.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
Powered by blists - more mailing lists