mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Yangyu Chen <cyy@cyyself.name>
To: Palmer Dabbelt <palmer@rivosinc.com>
Cc: Charlie Jenkins <charlie@rivosinc.com>,
	Jonathan Corbet <corbet@lwn.net>,
	Paul Walmsley <paul.walmsley@sifive.com>,
	Albert Ou <aou@eecs.berkeley.edu>, Shuah Khan <shuah@kernel.org>,
	Levi Zim <rsworktech@outlook.com>,
	Alexandre Ghiti <alexghiti@rivosinc.com>,
	linux-doc@vger.kernel.org, linux-riscv@lists.infradead.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-kselftest@vger.kernel.org
Subject: Re: [PATCH 3/3] riscv: mm: Do not restrict mmap address based on hint
Date: Fri, 6 Sep 2024 01:15:04 +0800	[thread overview]
Message-ID: <tencent_B49BC6F11F5737662664B35196CF50904805@qq.com> (raw)
In-Reply-To: <mhng-ad0c8c3b-568a-484d-bc3d-49b56a11dcd6@palmer-ri-x1c9>



> On Sep 3, 2024, at 22:27, Palmer Dabbelt <palmer@rivosinc.com> wrote:
> 
> On Mon, 26 Aug 2024 19:24:38 PDT (-0700), cyy@cyyself.name wrote:
>> 
>> 
>>> On Aug 27, 2024, at 00:36, Charlie Jenkins <charlie@rivosinc.com> wrote:
>>> The hint address should not forcefully restrict the addresses returned
>>> by mmap as this causes mmap to report ENOMEM when there is memory still
>>> available.
>> 
>> Fixing in this way will break userspace on Sv57 machines as some
>> issues mentioned in the patch [1].
>> 
>> I suggest restricting to BIT(47) by default, like patch [2], to
>> align with kernel behavior on x86 and aarch64, and this does exist
>> on x86 and aarch64 for quite a long time. In that way, we will also
>> solve the problem mentioned in the first patch [1], as QEMU enables
>> Sv57 by default now and will not break userspace.
>> 
>> [1] https://lore.kernel.org/linux-riscv/20230809232218.849726-1-charlie@rivosinc.com/
>> [2] https://lore.kernel.org/linux-riscv/tencent_B2D0435BC011135736262764B511994F4805@qq.com/
> 
> I'm going to pick this up as it's a revert and a bug fix, so we can backport it.  If the right answer is to just forget about the sv39 userspace and only worry about sv48 userspace then your patches are likely the way to go,

I think we don't need to care about restricting to sv39 now since
the ASAN bug has been fixed. We should care about what to do to not
break userspace on sv57 machines as QEMU enables sv57 by default,
which is widely used.

> but there's a handful of discussions around that which might take a bit.
> 
>> 
>> Thanks,
>> Yangyu Chen
>> 
>>> Signed-off-by: Charlie Jenkins <charlie@rivosinc.com>
>>> Fixes: b5b4287accd7 ("riscv: mm: Use hint address in mmap if available")
>>> Fixes: add2cc6b6515 ("RISC-V: mm: Restrict address space for sv39,sv48,sv57")
>>> Closes: https://lore.kernel.org/linux-kernel/ZbxTNjQPFKBatMq+@ghost/T/#mccb1890466bf5a488c9ce7441e57e42271895765
>>> ---
>>> arch/riscv/include/asm/processor.h | 26 ++------------------------
>>> 1 file changed, 2 insertions(+), 24 deletions(-)
>>> diff --git a/arch/riscv/include/asm/processor.h b/arch/riscv/include/asm/processor.h
>>> index 8702b8721a27..efa1b3519b23 100644
>>> --- a/arch/riscv/include/asm/processor.h
>>> +++ b/arch/riscv/include/asm/processor.h
>>> @@ -14,36 +14,14 @@
>>> #include <asm/ptrace.h>
>>> -/*
>>> - * addr is a hint to the maximum userspace address that mmap should provide, so
>>> - * this macro needs to return the largest address space available so that
>>> - * mmap_end < addr, being mmap_end the top of that address space.
>>> - * See Documentation/arch/riscv/vm-layout.rst for more details.
>>> - */
>>> #define arch_get_mmap_end(addr, len, flags) \
>>> ({ \
>>> - unsigned long mmap_end; \
>>> - typeof(addr) _addr = (addr); \
>>> - if ((_addr) == 0 || is_compat_task() || \
>>> -    ((_addr + len) > BIT(VA_BITS - 1))) \
>>> - mmap_end = STACK_TOP_MAX; \
>>> - else \
>>> - mmap_end = (_addr + len); \
>>> - mmap_end; \
>>> + STACK_TOP_MAX; \
>>> })
>>> #define arch_get_mmap_base(addr, base) \
>>> ({ \
>>> - unsigned long mmap_base; \
>>> - typeof(addr) _addr = (addr); \
>>> - typeof(base) _base = (base); \
>>> - unsigned long rnd_gap = DEFAULT_MAP_WINDOW - (_base); \
>>> - if ((_addr) == 0 || is_compat_task() || \
>>> -    ((_addr + len) > BIT(VA_BITS - 1))) \
>>> - mmap_base = (_base); \
>>> - else \
>>> - mmap_base = (_addr + len) - rnd_gap; \
>>> - mmap_base; \
>>> + base; \
>>> })
>>> #ifdef CONFIG_64BIT
>>> -- 
>>> 2.45.0


  reply	other threads:[~2024-09-05 17:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-26 16:36 [PATCH 0/3] " Charlie Jenkins
2024-08-26 16:36 ` [PATCH 1/3] Revert "RISC-V: mm: Document mmap changes" Charlie Jenkins
2024-08-26 16:36 ` [PATCH 2/3] riscv: selftests: Remove mmap hint address checks Charlie Jenkins
2024-08-26 16:36 ` [PATCH 3/3] riscv: mm: Do not restrict mmap address based on hint Charlie Jenkins
2024-08-27  2:24   ` Yangyu Chen
2024-09-03 14:27     ` Palmer Dabbelt
2024-09-05 17:15       ` Yangyu Chen [this message]
2024-08-31  3:33   ` Levi Zim
2024-09-03 14:30 ` [PATCH 0/3] " 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=tencent_B49BC6F11F5737662664B35196CF50904805@qq.com \
    --to=cyy@cyyself.name \
    --cc=alexghiti@rivosinc.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=charlie@rivosinc.com \
    --cc=corbet@lwn.net \
    --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@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®