linux-kernel - Re: [PATCH RESEND v4] riscv: mm: Fix the out of bound issue of vmemmap address

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: 
 <173643940874.1375203.8254463448578997209.git-patchwork-notify@kernel.org>
Date: Thu, 09 Jan 2025 16:16:48 +0000
From: patchwork-bot+linux-riscv@...nel.org
To: Xu Lu <luxu.kernel@...edance.com>
Cc: linux-riscv@...ts.infradead.org, paul.walmsley@...ive.com,
 palmer@...belt.com, alexghiti@...osinc.com, bjorn@...osinc.com,
 lihangjing@...edance.com, xieyongji@...edance.com,
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH RESEND v4] riscv: mm: Fix the out of bound issue of vmemmap
 address

Hello:

This patch was applied to riscv/linux.git (fixes)
by Palmer Dabbelt <palmer@...osinc.com>:

On Fri,  3 Jan 2025 17:20:23 +0800 you wrote:
> In sparse vmemmap model, the virtual address of vmemmap is calculated as:
> ((struct page *)VMEMMAP_START - (phys_ram_base >> PAGE_SHIFT)).
> And the struct page's va can be calculated with an offset:
> (vmemmap + (pfn)).
> 
> However, when initializing struct pages, kernel actually starts from the
> first page from the same section that phys_ram_base belongs to. If the
> first page's physical address is not (phys_ram_base >> PAGE_SHIFT), then
> we get an va below VMEMMAP_START when calculating va for it's struct page.
> 
> [...]

Here is the summary with links:
  - [RESEND,v4] riscv: mm: Fix the out of bound issue of vmemmap address
    https://git.kernel.org/riscv/c/f754f27e98f8

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