From: patchwork-bot+linux-riscv@kernel.org
To: Yangyu Chen <cyy@cyyself.name>
Cc: linux-riscv@lists.infradead.org, charlie@rivosinc.com,
corbet@lwn.net, paul.walmsley@sifive.com, palmer@dabbelt.com,
aou@eecs.berkeley.edu, shuah@kernel.org, rsworktech@outlook.com,
alexghiti@rivosinc.com, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, palmer@rivosinc.com,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v3 0/3] RISC-V: mm: do not treat hint addr on mmap as the upper bound to search
Date: Tue, 03 Sep 2024 14:30:42 +0000 [thread overview]
Message-ID: <172537384274.320952.7351958259552393532.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <tencent_108260B43689E30AAE5D0C7C085AA31ADF06@qq.com>
Hello:
This series was applied to riscv/linux.git (fixes)
by Palmer Dabbelt <palmer@rivosinc.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
WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+linux-riscv@kernel.org
To: Yangyu Chen <cyy@cyyself.name>
Cc: linux-riscv@lists.infradead.org, charlie@rivosinc.com,
corbet@lwn.net, paul.walmsley@sifive.com, palmer@dabbelt.com,
aou@eecs.berkeley.edu, shuah@kernel.org, rsworktech@outlook.com,
alexghiti@rivosinc.com, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, palmer@rivosinc.com,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v3 0/3] RISC-V: mm: do not treat hint addr on mmap as the upper bound to search
Date: Tue, 03 Sep 2024 14:30:42 +0000 [thread overview]
Message-ID: <172537384274.320952.7351958259552393532.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <tencent_108260B43689E30AAE5D0C7C085AA31ADF06@qq.com>
Hello:
This series was applied to riscv/linux.git (fixes)
by Palmer Dabbelt <palmer@rivosinc.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
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2024-09-03 14:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-27 8:05 [PATCH v3 0/3] RISC-V: mm: do not treat hint addr on mmap as the upper bound to search Yangyu Chen
2024-08-27 8:05 ` Yangyu Chen
2024-08-27 8:07 ` [PATCH v3 1/3] riscv: selftests: Remove mmap hint address checks Yangyu Chen
2024-08-27 8:07 ` Yangyu Chen
2024-08-27 8:07 ` [PATCH v3 2/3] RISC-V: mm: not use hint addr as upper bound Yangyu Chen
2024-08-27 8:07 ` Yangyu Chen
2024-08-27 8:07 ` [PATCH v3 3/3] Documentation: riscv: correct sv57 kernel behavior Yangyu Chen
2024-08-27 8:07 ` Yangyu Chen
2024-08-27 16:33 ` [PATCH v3 0/3] RISC-V: mm: do not treat hint addr on mmap as the upper bound to search Palmer Dabbelt
2024-08-27 16:33 ` Palmer Dabbelt
2024-08-27 16:40 ` Charlie Jenkins
2024-08-27 16:40 ` Charlie Jenkins
2024-08-27 18:04 ` Yangyu Chen
2024-08-27 18:04 ` Yangyu Chen
2024-08-27 19:35 ` Charlie Jenkins
2024-08-27 19:35 ` Charlie Jenkins
2024-08-27 17:47 ` Yangyu Chen
2024-08-27 17:47 ` Yangyu Chen
2024-09-03 14:30 ` patchwork-bot+linux-riscv [this message]
2024-09-03 14:30 ` patchwork-bot+linux-riscv
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=172537384274.320952.7351958259552393532.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=alexghiti@rivosinc.com \
--cc=aou@eecs.berkeley.edu \
--cc=charlie@rivosinc.com \
--cc=corbet@lwn.net \
--cc=cyy@cyyself.name \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=palmer@rivosinc.com \
--cc=paul.walmsley@sifive.com \
--cc=rsworktech@outlook.com \
--cc=shuah@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.