From: Sami Tolvanen <samitolvanen@google.com> To: Paul Walmsley <paul.walmsley@sifive.com>, Palmer Dabbelt <palmer@dabbelt.com>, Albert Ou <aou@eecs.berkeley.edu>, Andrew Morton <akpm@linux-foundation.org>, Kees Cook <keescook@chromium.org> Cc: linux-mm@kvack.org, linux-riscv@lists.infradead.org, llvm@lists.linux.dev, linux-kernel@vger.kernel.org, Sami Tolvanen <samitolvanen@google.com> Subject: [PATCH 0/2] riscv: Increase mmap_rnd_bits_max on Sv48/57 Date: Fri, 29 Sep 2023 21:11:56 +0000 [thread overview] Message-ID: <20230929211155.3910949-4-samitolvanen@google.com> (raw) Hi all, We noticed that 64-bit RISC-V kernels limit mmap_rnd_bits to 24 even if the hardware supports a larger virtual address space size [1]. These two patches allow mmap_rnd_bits_max to be changed during init, and bumps up the maximum randomness if we end up setting up 4/5-level paging at boot. Sami [1] https://github.com/google/android-riscv64/issues/1 Sami Tolvanen (2): mm: Change mmap_rnd_bits_max to __ro_after_init riscv: mm: Update mmap_rnd_bits_max arch/riscv/mm/init.c | 6 ++++++ include/linux/mm.h | 2 +- mm/mmap.c | 2 +- 3 files changed, 8 insertions(+), 2 deletions(-) base-commit: 6465e260f48790807eef06b583b38ca9789b6072 -- 2.42.0.582.g8ccd20d70d-goog
WARNING: multiple messages have this Message-ID (diff)
From: Sami Tolvanen <samitolvanen@google.com> To: Paul Walmsley <paul.walmsley@sifive.com>, Palmer Dabbelt <palmer@dabbelt.com>, Albert Ou <aou@eecs.berkeley.edu>, Andrew Morton <akpm@linux-foundation.org>, Kees Cook <keescook@chromium.org> Cc: linux-mm@kvack.org, linux-riscv@lists.infradead.org, llvm@lists.linux.dev, linux-kernel@vger.kernel.org, Sami Tolvanen <samitolvanen@google.com> Subject: [PATCH 0/2] riscv: Increase mmap_rnd_bits_max on Sv48/57 Date: Fri, 29 Sep 2023 21:11:56 +0000 [thread overview] Message-ID: <20230929211155.3910949-4-samitolvanen@google.com> (raw) Hi all, We noticed that 64-bit RISC-V kernels limit mmap_rnd_bits to 24 even if the hardware supports a larger virtual address space size [1]. These two patches allow mmap_rnd_bits_max to be changed during init, and bumps up the maximum randomness if we end up setting up 4/5-level paging at boot. Sami [1] https://github.com/google/android-riscv64/issues/1 Sami Tolvanen (2): mm: Change mmap_rnd_bits_max to __ro_after_init riscv: mm: Update mmap_rnd_bits_max arch/riscv/mm/init.c | 6 ++++++ include/linux/mm.h | 2 +- mm/mmap.c | 2 +- 3 files changed, 8 insertions(+), 2 deletions(-) base-commit: 6465e260f48790807eef06b583b38ca9789b6072 -- 2.42.0.582.g8ccd20d70d-goog _______________________________________________ linux-riscv mailing list linux-riscv@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2023-09-29 21:11 UTC|newest] Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-29 21:11 Sami Tolvanen [this message] 2023-09-29 21:11 ` [PATCH 0/2] riscv: Increase mmap_rnd_bits_max on Sv48/57 Sami Tolvanen 2023-09-29 21:11 ` [PATCH 1/2] mm: Change mmap_rnd_bits_max to __ro_after_init Sami Tolvanen 2023-09-29 21:11 ` Sami Tolvanen 2023-09-29 21:55 ` Kees Cook 2023-09-29 21:55 ` Kees Cook 2023-09-29 21:11 ` [PATCH 2/2] riscv: mm: Update mmap_rnd_bits_max Sami Tolvanen 2023-09-29 21:11 ` Sami Tolvanen 2023-09-29 21:54 ` Kees Cook 2023-09-29 21:54 ` Kees Cook 2023-09-29 22:52 ` Sami Tolvanen 2023-09-29 22:52 ` Sami Tolvanen 2023-09-30 9:02 ` Conor Dooley 2023-09-30 9:02 ` Conor Dooley 2023-09-30 21:01 ` Kees Cook 2023-09-30 21:01 ` Kees Cook 2023-10-01 15:19 ` Pedro Falcato 2023-10-01 15:19 ` Pedro Falcato 2023-10-02 7:02 ` Alexandre Ghiti 2023-10-02 7:02 ` Alexandre Ghiti 2023-10-02 15:58 ` Sami Tolvanen 2023-10-02 15:58 ` Sami Tolvanen 2023-12-06 13:14 ` [PATCH 0/2] riscv: Increase mmap_rnd_bits_max on Sv48/57 Palmer Dabbelt 2023-12-06 13:14 ` Palmer Dabbelt 2023-12-06 20:28 ` Kees Cook 2023-12-06 20:28 ` Kees Cook 2024-01-17 20:29 ` Sami Tolvanen 2024-01-17 20:29 ` Sami Tolvanen 2024-01-25 21:30 ` patchwork-bot+linux-riscv 2024-01-25 21: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=20230929211155.3910949-4-samitolvanen@google.com \ --to=samitolvanen@google.com \ --cc=akpm@linux-foundation.org \ --cc=aou@eecs.berkeley.edu \ --cc=keescook@chromium.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mm@kvack.org \ --cc=linux-riscv@lists.infradead.org \ --cc=llvm@lists.linux.dev \ --cc=palmer@dabbelt.com \ --cc=paul.walmsley@sifive.com \ /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: linkBe 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.