From: Will Deacon <will@kernel.org> To: torvalds@linux-foundation.org Cc: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, catalin.marinas@arm.com, kernel-team@android.com Subject: [GIT PULL] arm64 fixes for -rc3 Date: Fri, 21 Feb 2020 16:01:26 +0000 [thread overview] Message-ID: <20200221160126.GB19330@willie-the-truck> (raw) Hi Linus, Please pull these arm64 fixes for -rc3. It's all straightforward apart from the changes to mmap()/mremap() in relation to their handling of address arguments from userspace with non-zero tag bits in the upper byte. The change to brk() is necessary to fix a nasty user-visible regression in malloc(), but we tightened up mmap() and mremap() at the same time because they also allow the user to create virtual aliases by accident. It's much less likely than brk() to matter in practice, but enforcing the principle of "don't permit the creation of mappings using tagged addresses" leads to a straightforward ABI without having to worry about the "but what if a crazy program did foo?" aspect of things. That said, this is core code and I know you'd prefer to limit the change to brk(), so the patch is sitting on top of the branch in case you prefer not to include it. If you decide to tweak it manually, please can you update the docs at the same time? Cheers, Will --->8 The following changes since commit d91771848f0ae2eec250a9345926a1a3558fa943: arm64: time: Replace <linux/clk-provider.h> by <linux/of_clk.h> (2020-02-12 17:26:38 +0000) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git tags/arm64-fixes for you to fetch changes up to dcde237319e626d1ec3c9d8b7613032f0fd4663a: mm: Avoid creating virtual address aliases in brk()/mmap()/mremap() (2020-02-20 10:03:14 +0000) ---------------------------------------------------------------- arm64 fixes for -rc3 - Fix regression in malloc() caused by ignored address tags in brk() - Add missing brackets around argument to untagged_addr() macro - Fix clang build when using binutils assembler - Fix silly typo in virtual memory map documentation ---------------------------------------------------------------- Catalin Marinas (1): mm: Avoid creating virtual address aliases in brk()/mmap()/mremap() Scott Branden (1): docs: arm64: fix trivial spelling enought to enough in memory.rst Vincenzo Frascino (1): arm64: lse: Fix LSE atomics with LLVM Will Deacon (1): arm64: memory: Add missing brackets to untagged_addr() macro Documentation/arm64/memory.rst | 2 +- Documentation/arm64/tagged-address-abi.rst | 11 +++++++++-- arch/arm64/include/asm/lse.h | 2 +- arch/arm64/include/asm/memory.h | 2 +- mm/mmap.c | 4 ---- mm/mremap.c | 1 - 6 files changed, 12 insertions(+), 10 deletions(-)
WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will@kernel.org> To: torvalds@linux-foundation.org Cc: catalin.marinas@arm.com, kernel-team@android.com, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org Subject: [GIT PULL] arm64 fixes for -rc3 Date: Fri, 21 Feb 2020 16:01:26 +0000 [thread overview] Message-ID: <20200221160126.GB19330@willie-the-truck> (raw) Hi Linus, Please pull these arm64 fixes for -rc3. It's all straightforward apart from the changes to mmap()/mremap() in relation to their handling of address arguments from userspace with non-zero tag bits in the upper byte. The change to brk() is necessary to fix a nasty user-visible regression in malloc(), but we tightened up mmap() and mremap() at the same time because they also allow the user to create virtual aliases by accident. It's much less likely than brk() to matter in practice, but enforcing the principle of "don't permit the creation of mappings using tagged addresses" leads to a straightforward ABI without having to worry about the "but what if a crazy program did foo?" aspect of things. That said, this is core code and I know you'd prefer to limit the change to brk(), so the patch is sitting on top of the branch in case you prefer not to include it. If you decide to tweak it manually, please can you update the docs at the same time? Cheers, Will --->8 The following changes since commit d91771848f0ae2eec250a9345926a1a3558fa943: arm64: time: Replace <linux/clk-provider.h> by <linux/of_clk.h> (2020-02-12 17:26:38 +0000) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git tags/arm64-fixes for you to fetch changes up to dcde237319e626d1ec3c9d8b7613032f0fd4663a: mm: Avoid creating virtual address aliases in brk()/mmap()/mremap() (2020-02-20 10:03:14 +0000) ---------------------------------------------------------------- arm64 fixes for -rc3 - Fix regression in malloc() caused by ignored address tags in brk() - Add missing brackets around argument to untagged_addr() macro - Fix clang build when using binutils assembler - Fix silly typo in virtual memory map documentation ---------------------------------------------------------------- Catalin Marinas (1): mm: Avoid creating virtual address aliases in brk()/mmap()/mremap() Scott Branden (1): docs: arm64: fix trivial spelling enought to enough in memory.rst Vincenzo Frascino (1): arm64: lse: Fix LSE atomics with LLVM Will Deacon (1): arm64: memory: Add missing brackets to untagged_addr() macro Documentation/arm64/memory.rst | 2 +- Documentation/arm64/tagged-address-abi.rst | 11 +++++++++-- arch/arm64/include/asm/lse.h | 2 +- arch/arm64/include/asm/memory.h | 2 +- mm/mmap.c | 4 ---- mm/mremap.c | 1 - 6 files changed, 12 insertions(+), 10 deletions(-) _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2020-02-21 16:01 UTC|newest] Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-02-21 16:01 Will Deacon [this message] 2020-02-21 16:01 ` [GIT PULL] arm64 fixes for -rc3 Will Deacon 2020-02-22 0:07 ` Linus Torvalds 2020-02-22 0:07 ` Linus Torvalds 2020-02-22 0:15 ` pr-tracker-bot 2020-02-22 0:15 ` pr-tracker-bot -- strict thread matches above, loose matches on Subject: below -- 2024-02-02 11:11 Will Deacon 2024-02-02 11:11 ` Will Deacon 2024-02-02 20:43 ` pr-tracker-bot 2024-02-02 20:43 ` pr-tracker-bot 2023-09-22 16:19 Will Deacon 2023-09-22 16:19 ` Will Deacon 2023-09-22 20:19 ` pr-tracker-bot 2023-09-22 20:19 ` pr-tracker-bot 2023-05-19 11:46 Will Deacon 2023-05-19 11:46 ` Will Deacon 2023-05-19 18:32 ` pr-tracker-bot 2023-05-19 18:32 ` pr-tracker-bot 2022-08-26 17:58 Will Deacon 2022-08-26 17:58 ` Will Deacon 2022-08-26 19:09 ` pr-tracker-bot 2022-08-26 19:09 ` pr-tracker-bot 2021-11-26 13:22 Will Deacon 2021-11-26 13:22 ` Will Deacon 2021-11-26 18:35 ` pr-tracker-bot 2021-11-26 18:35 ` pr-tracker-bot 2021-07-22 15:55 Will Deacon 2021-07-22 15:55 ` Will Deacon 2021-07-22 18:00 ` pr-tracker-bot 2021-07-22 18:00 ` pr-tracker-bot 2021-03-12 13:34 [GIT PULL] arm64: Fixes " Will Deacon 2021-03-12 13:34 ` Will Deacon 2021-03-12 20:03 ` pr-tracker-bot 2021-03-12 20:03 ` pr-tracker-bot 2020-11-06 13:20 [GIT PULL] arm64 fixes " Will Deacon 2020-11-06 13:20 ` Will Deacon 2020-11-06 21:13 ` pr-tracker-bot 2020-11-06 21:13 ` pr-tracker-bot 2020-06-26 13:21 Will Deacon 2020-06-26 13:21 ` Will Deacon 2020-06-27 16:00 ` pr-tracker-bot 2020-06-27 16:00 ` pr-tracker-bot 2019-10-09 13:30 [GIT PULL] arm64: Fixes " Will Deacon 2019-10-09 13:30 ` Will Deacon 2019-10-09 19:30 ` pr-tracker-bot 2019-10-09 19:30 ` pr-tracker-bot 2019-05-30 16:11 [GIT PULL] arm64: fixes " Will Deacon 2019-05-30 16:11 ` Will Deacon 2019-05-31 4:25 ` pr-tracker-bot 2019-05-31 4:25 ` pr-tracker-bot 2019-01-20 0:04 Will Deacon 2019-01-20 0:04 ` Will Deacon 2019-01-20 3:29 ` Linus Torvalds 2019-01-20 3:29 ` Linus Torvalds 2019-01-20 4:00 ` pr-tracker-bot 2019-01-20 4:00 ` pr-tracker-bot 2018-04-27 16:23 Will Deacon 2018-04-27 16:23 ` Will Deacon 2017-12-07 17:58 Will Deacon 2017-12-07 17:58 ` Will Deacon 2016-10-28 16:01 Will Deacon 2016-10-28 16:01 ` Will Deacon 2016-02-04 18:49 Will Deacon 2016-02-04 18:49 ` Will Deacon
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=20200221160126.GB19330@willie-the-truck \ --to=will@kernel.org \ --cc=catalin.marinas@arm.com \ --cc=kernel-team@android.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=torvalds@linux-foundation.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: 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.