From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] arm64 fixes for 4.10-rc5
Date: Fri, 20 Jan 2017 13:52:52 +0000 [thread overview]
Message-ID: <20170120135249.GA19095@e104818-lin.cambridge.arm.com> (raw)
Hi Linus,
Please pull the arm64 fixes below for 4.10. Thanks.
The following changes since commit 49def1853334396f948dcb4cedb9347abb318df5:
Linux 4.10-rc4 (2017-01-15 16:21:59 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux tags/arm64-fixes
for you to fetch changes up to 7d9e8f71b989230bc613d121ca38507d34ada849:
arm64: avoid returning from bad_mode (2017-01-19 15:38:22 +0000)
----------------------------------------------------------------
- Avoid potential stack information leak via the ptrace ABI caused by
uninitialised variables
- SWIOTLB DMA API fall-back allocation fix when the SWIOTLB buffer is
not initialised (all RAM is suitable for 32-bit DMA masks)
- Fix the bad_mode function returning for unhandled exceptions coming
from user space
- Fix name clash in __page_to_voff()
----------------------------------------------------------------
Alexander Graf (1):
arm64: Fix swiotlb fallback allocation
Dave Martin (5):
arm64/ptrace: Preserve previous registers for short regset write
arm64/ptrace: Preserve previous registers for short regset write
arm64/ptrace: Preserve previous registers for short regset write
arm64/ptrace: Avoid uninitialised struct padding in fpr_set()
arm64/ptrace: Reject attempts to set incomplete hardware breakpoint fields
Mark Rutland (1):
arm64: avoid returning from bad_mode
Oleksandr Andrushchenko (1):
arm64: mm: avoid name clash in __page_to_voff()
arch/arm64/include/asm/memory.h | 2 +-
arch/arm64/include/uapi/asm/ptrace.h | 1 +
arch/arm64/kernel/entry.S | 2 +-
arch/arm64/kernel/ptrace.c | 16 +++++++++++-----
arch/arm64/kernel/traps.c | 28 ++++++++++++++++++++++++----
arch/arm64/mm/init.c | 2 ++
6 files changed, 40 insertions(+), 11 deletions(-)
--
Catalin
reply other threads:[~2017-01-20 13:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20170120135249.GA19095@e104818-lin.cambridge.arm.com \
--to=catalin.marinas@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).