From: Will Deacon <will@kernel.org>
To: torvalds@linux-foundation.org
Cc: catalin.marinas@arm.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux ARM Kernel Mailing List
<linux-arm-kernel@lists.infradead.org>
Subject: [GIT PULL] arm64: Fix for -rc7
Date: Fri, 8 Nov 2019 10:32:31 +0000 [thread overview]
Message-ID: <20191108103231.GA19153@willie-the-truck> (raw)
Hi Linus,
Please pull this single arm64 fix for -rc7. It's a revert of 747a70e60b72
("arm64: Fix copy-on-write referencing in HugeTLB"), not because that
patch was wrong, but because it was broken by aa57157be69f ("arm64: Ensure
VM_WRITE|VM_SHARED ptes are clean by default") which we merged in -rc6.
We spotted the issue in Android (AOSP), where one of the JIT threads gets
stuck on a write fault during boot because the faulting pte is marked as
PTE_DIRTY | PTE_WRITE | PTE_RDONLY and the fault handler decides that
there's nothing to do thanks to pte_same() masking out PTE_RDONLY.
Thanks to John Stultz for reporting this and testing this so quickly, and
to Steve Capper for confirming that the HugeTLB tests continue to pass.
Cheers,
Will
--->8
The following changes since commit 1cf45b8fdbb87040e1d1bd793891089f4678aa41:
arm64: apply ARM64_ERRATUM_843419 workaround for Brahma-B53 core (2019-11-01 10:47:37 +0000)
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 6767df245f4736d0cf0c6fb7cf9cf94b27414245:
arm64: Do not mask out PTE_RDONLY in pte_same() (2019-11-06 19:31:56 +0000)
----------------------------------------------------------------
arm64 fix for -rc7
- Fix pte_same() to avoid getting stuck on write fault
----------------------------------------------------------------
Catalin Marinas (1):
arm64: Do not mask out PTE_RDONLY in pte_same()
arch/arm64/include/asm/pgtable.h | 17 -----------------
1 file changed, 17 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-11-08 10:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-08 10:32 Will Deacon [this message]
2019-11-08 17:55 ` [GIT PULL] arm64: Fix for -rc7 pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2020-07-24 11:52 [GIT PULL] arm64 fix " Will Deacon
2020-07-24 21:40 ` pr-tracker-bot
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=20191108103231.GA19153@willie-the-truck \
--to=will@kernel.org \
--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