[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<172537384274.320952.7351958259552393532.git-patchwork-notify@kernel.org>
Date: Tue, 03 Sep 2024 14:30:42 +0000
From: patchwork-bot+linux-riscv@...nel.org
To: Yangyu Chen <cyy@...self.name>
Cc: linux-riscv@...ts.infradead.org, charlie@...osinc.com, corbet@....net,
paul.walmsley@...ive.com, palmer@...belt.com, aou@...s.berkeley.edu,
shuah@...nel.org, rsworktech@...look.com, alexghiti@...osinc.com,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org, palmer@...osinc.com,
linux-kselftest@...r.kernel.org
Subject: Re: [PATCH v3 0/3] RISC-V: mm: do not treat hint addr on mmap as the
upper bound to search
Hello:
This series was applied to riscv/linux.git (fixes)
by Palmer Dabbelt <palmer@...osinc.com>:
On Tue, 27 Aug 2024 16:05:15 +0800 you wrote:
> Previous patch series[1][2] changes a mmap behavior that treats the hint
> address as the upper bound of the mmap address range. The motivation of the
> previous patch series is that some user space software may assume 48-bit
> address space and use higher bits to encode some information, which may
> collide with large virtual address space mmap may return. However, to make
> sv48 by default, we don't need to change the meaning of the hint address on
> mmap as the upper bound of the mmap address range. This behavior breaks
> some user space software like Chromium that gets ENOMEM error when the hint
> address + size is not big enough, as specified in [3].
>
> [...]
Here is the summary with links:
- [v3,1/3] riscv: selftests: Remove mmap hint address checks
https://git.kernel.org/riscv/c/83dae72ac038
- [v3,2/3] RISC-V: mm: not use hint addr as upper bound
(no matching commit)
- [v3,3/3] Documentation: riscv: correct sv57 kernel behavior
(no matching commit)
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