From: Alexandre Ghiti <alex@ghiti.fr>
To: Christoph Hellwig <hch@infradead.org>,
Russell King <linux@armlinux.org.uk>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
Ralf Baechle <ralf@linux-mips.org>,
Paul Burton <paul.burton@mips.com>,
James Hogan <jhogan@kernel.org>,
Palmer Dabbelt <palmer@sifive.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Luis Chamberlain <mcgrof@kernel.org>,
Kees Cook <keescook@chromium.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-mips@vger.kernel.org,
linux-riscv@lists.infradead.org, linux-fsdevel@vger.kernel.org,
linux-mm@kvack.org
Cc: Alexandre Ghiti <alex@ghiti.fr>
Subject: [PATCH 0/4] Provide generic top-down mmap layout functions
Date: Fri, 22 Mar 2019 03:42:21 -0400 [thread overview]
Message-ID: <20190322074225.22282-1-alex@ghiti.fr> (raw)
This series introduces generic functions to make top-down mmap layout
easily accessible to architectures, in particular riscv which was
the initial goal of this series.
The generic implementation was taken from arm64 and used successively
by arm, mips and finally riscv.
Note that in addition the series fixes 2 issues:
- stack randomization was taken into account even if not necessary.
- [1] fixed an issue with mmap base which did not take into account
randomization but did not report it to arm and mips, so by moving
arm64 into a generic library, this problem is now fixed for both
architectures.
This work is an effort to factorize architecture functions to avoid
code duplication and oversights as in [1].
[1]: https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1429066.html
Alexandre Ghiti (4):
arm64, mm: Move generic mmap layout functions to mm
arm: Use generic mmap top-down layout
mips: Use generic mmap top-down layout
riscv: Make mmap allocation top-down by default
arch/arm/include/asm/processor.h | 2 +-
arch/arm/mm/mmap.c | 52 ----------------
arch/arm64/include/asm/processor.h | 2 +-
arch/arm64/mm/mmap.c | 72 ----------------------
arch/mips/include/asm/processor.h | 4 +-
arch/mips/mm/mmap.c | 57 -----------------
arch/riscv/Kconfig | 12 ++++
arch/riscv/include/asm/processor.h | 1 +
fs/binfmt_elf.c | 20 ------
include/linux/mm.h | 2 +
kernel/sysctl.c | 6 +-
mm/util.c | 99 +++++++++++++++++++++++++++++-
12 files changed, 121 insertions(+), 208 deletions(-)
--
2.20.1
next reply other threads:[~2019-03-22 7:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-22 7:42 Alexandre Ghiti [this message]
2019-03-22 7:42 ` [PATCH 1/4] arm64, mm: Move generic mmap layout functions to mm Alexandre Ghiti
2019-03-22 13:21 ` Christoph Hellwig
2019-03-23 8:18 ` Alex Ghiti
2019-03-22 7:42 ` [PATCH 2/4] arm: Use generic mmap top-down layout Alexandre Ghiti
2019-03-22 7:42 ` [PATCH 3/4] mips: " Alexandre Ghiti
2019-03-22 7:42 ` [PATCH 4/4] riscv: Make mmap allocation top-down by default Alexandre Ghiti
2019-03-22 13:22 ` Christoph Hellwig
2019-03-23 8:05 ` Alex Ghiti
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=20190322074225.22282-1-alex@ghiti.fr \
--to=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=catalin.marinas@arm.com \
--cc=hch@infradead.org \
--cc=jhogan@kernel.org \
--cc=keescook@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=mcgrof@kernel.org \
--cc=palmer@sifive.com \
--cc=paul.burton@mips.com \
--cc=ralf@linux-mips.org \
--cc=viro@zeniv.linux.org.uk \
--cc=will.deacon@arm.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: 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;
as well as URLs for NNTP newsgroup(s).