From: Mark Rutland <mark.rutland@arm.com>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org, akpm@linux-foundation.org,
andreyknvl@google.com, catalin.marinas@arm.com,
dvyukov@google.com, glider@google.com, ryabinin.a.a@gmail.com,
sdonthineni@nvidia.com, will@kernel.org
Subject: Re: [PATCH v2 0/6] arm64: module: improve module VA range selection
Date: Tue, 30 May 2023 11:38:04 +0100 [thread overview]
Message-ID: <ZHXSDK+ajflWnK+q@FVFF77S0Q05N> (raw)
In-Reply-To: <CAMj1kXG2g6LVi0PZ2kxSTqd9BVOkJdNiZwb-UuD5bBLj5PyxNg@mail.gmail.com>
On Tue, May 30, 2023 at 12:31:54PM +0200, Ard Biesheuvel wrote:
> On Fri, 12 May 2023 at 17:22, Mark Rutland <mark.rutland@arm.com> wrote:
> >
> > This series (based on v6.4-rc1) aims to make arm64's module allocation
> > code more robust. [...]
> > Mark Rutland (6):
> > arm64: module: remove old !KASAN_VMALLOC logic
> > arm64: kasan: remove !KASAN_VMALLOC remnants
> > arm64: kaslr: split kaslr/module initialization
> > arm64: module: move module randomization to module.c
> > arm64: module: mandate MODULE_PLTS
> > arm64: module: rework module VA range selection
>
> For the series,
>
> Reviewed-by: Ard Biesheuvel <ardb@kernel.org>
Thanks!
> (I spotted some typos in the commit log somewhere, please refer to my
> other reply)
Sorry about that; I spotted a few more when fixing that up, so I'll check the
entire series and post a v3 with all of that corrected.
Mark.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2023-05-30 10:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230512152210.3072475-1-mark.rutland@arm.com>
[not found] ` <20230512152210.3072475-4-mark.rutland@arm.com>
2023-05-30 10:26 ` [PATCH v2 3/6] arm64: kaslr: split kaslr/module initialization Ard Biesheuvel
2023-05-30 10:31 ` [PATCH v2 0/6] arm64: module: improve module VA range selection Ard Biesheuvel
2023-05-30 10:38 ` Mark Rutland [this message]
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=ZHXSDK+ajflWnK+q@FVFF77S0Q05N \
--to=mark.rutland@arm.com \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@google.com \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=ryabinin.a.a@gmail.com \
--cc=sdonthineni@nvidia.com \
--cc=will@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