From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] arm64: couple of fixes for -rc5
Date: Fri, 12 Sep 2014 15:39:36 +0100 [thread overview]
Message-ID: <20140912143936.GI6871@arm.com> (raw)
Hi Linus,
Please can you pull these two arm64 fixes for -rc5? The IRQ migration fix
turned up late last time and there's also a TLS leaking issue that we
just fixed for arch/arm/ too.
To keep things interesting, I've signed the tag using my Yubikey from KS.
Given that it only supports 2048-bit keys, I've used a new subkey so you
may need to update your keyring to verify the signature.
Cheers,
Will
--->8
The following changes since commit 5e39977edf6500fd12f169e6c458d33b0ef62feb:
Revert "arm64: cpuinfo: print info for all CPUs" (2014-09-01 15:55:22 +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 eb35bdd7bca29a13c8ecd44e6fd747a84ce675db:
arm64: flush TLS registers during exec (2014-09-11 18:34:58 +0100)
----------------------------------------------------------------
arm64 fixes for -rc5
Just a couple of stragglers here:
- Fix an issue migrating interrupts on CPU hotplug
- Fix a potential information leak of TLS registers across an exec
(Nathan has sent a corresponding patch for arch/arm/ to rmk)
----------------------------------------------------------------
Sudeep Holla (1):
arm64: use irq_set_affinity with force=false when migrating irqs
Will Deacon (1):
arm64: flush TLS registers during exec
arch/arm64/kernel/irq.c | 12 ++++--------
arch/arm64/kernel/process.c | 18 ++++++++++++++++++
arch/arm64/kernel/sys_compat.c | 6 ++++++
3 files changed, 28 insertions(+), 8 deletions(-)
next reply other threads:[~2014-09-12 14:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-12 14:39 Will Deacon [this message]
2014-09-12 16:55 ` [GIT PULL] arm64: couple of fixes for -rc5 Linus Torvalds
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=20140912143936.GI6871@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).