From: Will Deacon <will.deacon@arm.com>
To: torvalds@linux-foundation.org
Cc: catalin.marinas@arm.com, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, ebiederm@xmission.com
Subject: [GIT PULL] arm64: fixes for -rc3
Date: Thu, 30 May 2019 17:11:26 +0100 [thread overview]
Message-ID: <20190530161126.GB16230@fuggles.cambridge.arm.com> (raw)
Hi Linus,
The fixes are still trickling in for arm64, but the only really significant
one here is actually fixing a regression in the botched module relocation
range checking merged for -rc2. Hopefully we've nailed it this time.
Please pull.
Thanks,
Will
--->8
The following changes since commit edbcf50eb8aea5f81ae6d83bb969cb0bc02805a1:
arm64: insn: Add BUILD_BUG_ON() for invalid masks (2019-05-24 14:58:30 +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 1e29ab3186e33c77dbb2d7566172a205b59fa390:
arm64: use the correct function type for __arm64_sys_ni_syscall (2019-05-29 13:46:00 +0100)
----------------------------------------------------------------
arm64 fixes for -rc3
- Fix implementation of our set_personality() system call, which wasn't
being wrapped properly
- Fix system call function types to keep CFI happy
- Fix siginfo layout when delivering SIGKILL after a kernel fault
- Really fix module relocation range checking
----------------------------------------------------------------
Ard Biesheuvel (1):
arm64/module: revert to unsigned interpretation of ABS16/32 relocations
Catalin Marinas (1):
arm64: Fix the arm64_personality() syscall wrapper redirection
Eric W. Biederman (1):
signal/arm64: Use force_sig not force_sig_fault for SIGKILL
Sami Tolvanen (3):
arm64: fix syscall_fn_t type
arm64: use the correct function type in SYSCALL_DEFINE0
arm64: use the correct function type for __arm64_sys_ni_syscall
arch/arm64/include/asm/syscall.h | 2 +-
arch/arm64/include/asm/syscall_wrapper.h | 18 +++++++--------
arch/arm64/kernel/module.c | 38 +++++++++++++++++++++++++-------
arch/arm64/kernel/sys.c | 16 +++++++++-----
arch/arm64/kernel/sys32.c | 7 ++----
arch/arm64/kernel/traps.c | 5 ++++-
6 files changed, 56 insertions(+), 30 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:[~2019-05-30 16:11 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-30 16:11 Will Deacon [this message]
2019-05-31 4:25 ` [GIT PULL] arm64: fixes for -rc3 pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2024-02-02 11:11 [GIT PULL] arm64 " Will Deacon
2024-02-02 20:43 ` pr-tracker-bot
2023-09-22 16:19 Will Deacon
2023-09-22 20:19 ` pr-tracker-bot
2023-05-19 11:46 Will Deacon
2023-05-19 18:32 ` pr-tracker-bot
2022-08-26 17:58 Will Deacon
2022-08-26 19:09 ` pr-tracker-bot
2021-11-26 13:22 Will Deacon
2021-11-26 18:35 ` pr-tracker-bot
2021-07-22 15:55 Will Deacon
2021-07-22 18:00 ` pr-tracker-bot
2021-03-12 13:34 [GIT PULL] arm64: Fixes " Will Deacon
2021-03-12 20:03 ` pr-tracker-bot
2020-11-06 13:20 [GIT PULL] arm64 fixes " Will Deacon
2020-11-06 21:13 ` pr-tracker-bot
2020-06-26 13:21 Will Deacon
2020-06-27 16:00 ` pr-tracker-bot
2020-02-21 16:01 Will Deacon
2020-02-22 0:07 ` Linus Torvalds
2020-02-22 0:15 ` pr-tracker-bot
2019-10-09 13:30 [GIT PULL] arm64: Fixes " Will Deacon
2019-10-09 19:30 ` pr-tracker-bot
2019-01-20 0:04 [GIT PULL] arm64: fixes " Will Deacon
2019-01-20 3:29 ` Linus Torvalds
2019-01-20 4:00 ` pr-tracker-bot
2018-04-27 16:23 Will Deacon
2017-12-07 17:58 Will Deacon
2016-10-28 16:01 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=20190530161126.GB16230@fuggles.cambridge.arm.com \
--to=will.deacon@arm.com \
--cc=catalin.marinas@arm.com \
--cc=ebiederm@xmission.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: 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).