LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Will Deacon <will.deacon@arm.com>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, catalin.marinas@arm.com,
	dave.martin@arm.com
Subject: [GIT PULL] arm64: fixes for -rc3
Date: Thu, 7 Dec 2017 17:58:12 +0000	[thread overview]
Message-ID: <20171207175811.GL15393@arm.com> (raw)

Hi Linus,

Please pull the following arm64 fixes for 4.15-rc3.

Details in the tag, but they broadly fix some more FP register fallout
from the SVE patches and also some problems with the PGD tracking in our
software PAN emulation code, after we received a crash report from a 3.18
kernel running a backport.

Cheers,

Will

--->8

The following changes since commit ae64f9bd1d3621b5e60d7363bc20afb46aede215:

  Linux 4.15-rc2 (2017-12-03 11:01:47 -0500)

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 cb968afc789821cdf9e17e79ef08ab90e5bae0f2:

  arm64/sve: Avoid dereference of dead task_struct in KVM guest entry (2017-12-06 19:08:05 +0000)

----------------------------------------------------------------
arm64 fixes:

- Fix SW PAN pgd shadowing for kernel threads, EFI and exiting user tasks

- Fix FP register leak when a task_struct is re-allocated

- Fix potential use-after-free in FP state tracking used by KVM

----------------------------------------------------------------
Dave Martin (3):
      arm64: fpsimd: Prevent registers leaking from dead tasks
      arm64: fpsimd: Abstract out binding of task's fpsimd context to the cpu.
      arm64/sve: Avoid dereference of dead task_struct in KVM guest entry

Will Deacon (2):
      arm64: SW PAN: Point saved ttbr0 at the zero page when switching to init_mm
      arm64: SW PAN: Update saved ttbr0 value on enter_lazy_tlb

 arch/arm64/include/asm/efi.h         |  4 +--
 arch/arm64/include/asm/mmu_context.h | 46 ++++++++++++++++----------------
 arch/arm64/kernel/fpsimd.c           | 51 +++++++++++++++++++++---------------
 arch/arm64/kernel/process.c          |  9 +++++++
 4 files changed, 63 insertions(+), 47 deletions(-)

             reply	other threads:[~2017-12-07 17:58 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-07 17:58 Will Deacon [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-11-26 13:22 [GIT PULL] arm64 " 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-05-30 16:11 [GIT PULL] arm64: fixes " Will Deacon
2019-05-31  4:25 ` pr-tracker-bot
2019-01-20  0:04 Will Deacon
2019-01-20  3:29 ` Linus Torvalds
2019-01-20  4:00 ` pr-tracker-bot
2018-04-27 16:23 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=20171207175811.GL15393@arm.com \
    --to=will.deacon@arm.com \
    --cc=catalin.marinas@arm.com \
    --cc=dave.martin@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --subject='Re: [GIT PULL] arm64: fixes for -rc3' \
    /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

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).