From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] arm64: fixes for -rc1
Date: Fri, 5 Aug 2016 16:48:47 +0100 [thread overview]
Message-ID: <20160805154847.GD13272@arm.com> (raw)
Hi Linus,
Please pull these arm64 fixes for -rc1. The branch is based on the
for-next/core tag you pulled from Catalin last week. He's on holiday
once again, so I'm handling the fixes until he's back.
Details in the tag.
Cheers,
Will
--->8
The following changes since commit fd6380b75065fd2ff51b5f7cbbe6be77d71ea9c7:
arm64: arm: Fix-up the removal of the arm64 regs_query_register_name() prototype (2016-07-27 08:15:42 +0100)
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 747a70e60b7234e8fd9c35dd2f2db10ac1db231d:
arm64: Fix copy-on-write referencing in HugeTLB (2016-08-04 13:41:18 +0100)
----------------------------------------------------------------
arm64 fixes:
- Fix HugeTLB leak due to CoW and PTE_RDONLY mismatch
- Avoid accessing unmapped FDT fields when checking validity
- Correctly account for vDSO AUX entry in ARCH_DLINFO
- Fix kallsyms with absolute expressions in linker script
- Kill unnecessary symbol-based relocs in vmlinux
----------------------------------------------------------------
Ard Biesheuvel (3):
arm64: vmlinux.lds: make __rela_offset and __dynsym_offset ABSOLUTE
arm64: relocatable: suppress R_AARCH64_ABS64 relocations in vmlinux
arm64: mm: avoid fdt_check_header() before the FDT is fully mapped
James Hogan (1):
arm64: Define AT_VECTOR_SIZE_ARCH for ARCH_DLINFO
Steve Capper (1):
arm64: Fix copy-on-write referencing in HugeTLB
arch/arm64/Makefile | 2 +-
arch/arm64/include/asm/elf.h | 1 +
arch/arm64/include/asm/pgtable.h | 17 +++++++++++++++++
arch/arm64/include/uapi/asm/auxvec.h | 2 ++
arch/arm64/kernel/head.S | 21 +++------------------
arch/arm64/kernel/vmlinux.lds.S | 13 ++-----------
arch/arm64/mm/mmu.c | 8 ++++----
7 files changed, 30 insertions(+), 34 deletions(-)
next reply other threads:[~2016-08-05 15:48 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-05 15:48 Will Deacon [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-19 16:05 [GIT PULL] arm64 fixes for -rc1 Will Deacon
2024-01-19 16:34 ` Rob Herring
2024-01-19 16:58 ` Rob Herring
2024-01-19 22:50 ` pr-tracker-bot
2023-09-08 15:30 Will Deacon
2023-09-08 20:00 ` pr-tracker-bot
2023-05-04 14:22 Will Deacon
2023-05-04 19:49 ` pr-tracker-bot
2022-12-16 15:51 Will Deacon
2022-12-16 19:50 ` pr-tracker-bot
2021-11-10 18:52 Will Deacon
2021-11-10 20:09 ` pr-tracker-bot
2021-02-26 11:09 [GIT PULL] arm64: Fixes " Will Deacon
2021-02-26 18:31 ` pr-tracker-bot
2019-09-20 13:37 Will Deacon
2019-09-20 19:10 ` pr-tracker-bot
2019-01-04 18:24 [GIT PULL] arm64: fixes " Will Deacon
2019-01-05 20:20 ` pr-tracker-bot
2017-03-01 4:51 [GIT PULL] arm64 " Will Deacon
2014-12-16 17:50 [GIT PULL] arm64: " 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=20160805154847.GD13272@arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).