public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Will Deacon <will.deacon@arm.com>
To: torvalds@linux-foundation.org
Cc: linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, catalin.marinas@arm.com
Subject: [GIT PULL] arm64: fixes for -rc4
Date: Fri, 4 Aug 2017 19:32:04 +0100	[thread overview]
Message-ID: <20170804183204.GB24125@arm.com> (raw)

Hi Linus,

Here are some more arm64 fixes for 4.13. The main one is the PTE race
with the hardware walker, but there are a couple of other things too.

Please pull,

Will

--->8

The following changes since commit 16f73eb02d7e1765ccab3d2018e0bd98eb93d973:

  Linux 4.13-rc3 (2017-07-30 12:40:36 -0700)

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 82cd588052815eb4146f9f7c5347ca5e32c56360:

  arm64: avoid overflow in VA_START and PAGE_OFFSET (2017-08-04 15:06:35 +0100)

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

- Report correct timer frequency to userspace when trapping CNTFRQ_EL0

- Fix race with hardware page table updates when updating access flags

- Silence clang overflow warning in VA_START and PAGE_OFFSET calculations

----------------------------------------------------------------
Catalin Marinas (1):
      arm64: Fix potential race with hardware DBM in ptep_set_access_flags()

Marc Zyngier (1):
      arm64: Use arch_timer_get_rate when trapping CNTFRQ_EL0

Nick Desaulniers (1):
      arm64: avoid overflow in VA_START and PAGE_OFFSET

 arch/arm64/include/asm/memory.h |  6 ++++--
 arch/arm64/kernel/traps.c       |  2 +-
 arch/arm64/mm/fault.c           | 15 ++++++++-------
 3 files changed, 13 insertions(+), 10 deletions(-)

             reply	other threads:[~2017-08-04 18:32 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-04 18:32 Will Deacon [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-10-17 15:34 [GIT PULL] arm64 fixes for -rc4 Will Deacon
2024-10-17 17:34 ` pr-tracker-bot
2023-01-13 10:29 Will Deacon
2023-01-13 13:58 ` pr-tracker-bot
2022-09-02 11:12 Will Deacon
2022-09-02 18:30 ` pr-tracker-bot
2022-04-22 11:20 Will Deacon
2022-04-22 21:19 ` pr-tracker-bot
2021-12-03 13:19 Will Deacon
2021-12-03 18:53 ` pr-tracker-bot
2020-11-13 12:39 GIT " Will Deacon
2020-11-13 12:44 ` [GIT " Will Deacon
2020-11-13 17:25   ` Linus Torvalds
2020-07-04 13:05 Will Deacon
2020-07-05 17:35 ` pr-tracker-bot
2019-10-17 23:43 [GIT PULL] arm64: Fixes " Will Deacon
2019-10-18  0:06 ` Linus Torvalds
2019-10-18 17:41   ` Will Deacon
2019-10-18 19:17     ` Linus Torvalds
2019-10-21  6:46       ` Ingo Molnar
2019-10-21 11:45         ` Linus Torvalds
2019-10-22  8:16         ` Uwe Kleine-König
2019-10-18  0:15 ` pr-tracker-bot
2019-10-18 20:09 ` Jayachandran Chandrasekharan Nair
2019-06-07 15:13 [GIT PULL] arm64: fixes " Will Deacon
2019-06-07 16:45 ` pr-tracker-bot
2019-04-05 17:17 [GIT PULL] arm64 " Catalin Marinas
2019-04-05 23:50 ` pr-tracker-bot
2018-09-14 16:19 [GIT PULL] arm64: " Will Deacon
2017-12-15 18:31 Will Deacon
2016-06-17 17:07 Will Deacon
2015-05-14 15:48 Will Deacon
2015-01-09 15:22 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=20170804183204.GB24125@arm.com \
    --to=will.deacon@arm.com \
    --cc=catalin.marinas@arm.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