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 Subject: [GIT PULL] arm64: fixes for -rc7 Date: Fri, 25 May 2018 17:04:49 +0100 [thread overview] Message-ID: <20180525160448.GF3255@arm.com> (raw) Hi Linus, Here are a few arm64 fixes for -rc7. The two main fixes are for the asm constraints in our LSE atomics and for our pmd/pud setters when changing permissions for kernel mappings. Summary in the tag. Please pull, Will --->8 The following changes since commit 771c577c23bac90597c685971d7297ea00f99d11: Linux 4.17-rc6 (2018-05-20 15:31:38 -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 82034c23fcbc2389c73d97737f61fa2dd6526413: arm64: Make sure permission updates happen for pmd/pud (2018-05-24 11:19:31 +0100) ---------------------------------------------------------------- More arm64 fixes: - Fix application of read-only permissions to kernel section mappings - Sanitise reported ESR values for signals delivered on a kernel address - Ensure tishift GCC helpers are exported to modules - Fix inline asm constraints for some LSE atomics ---------------------------------------------------------------- Jason A. Donenfeld (1): arm64: export tishift functions to modules Laura Abbott (1): arm64: Make sure permission updates happen for pmd/pud Peter Maydell (1): arm64: fault: Don't leak data in ESR context for user fault on kernel VA Will Deacon (1): arm64: lse: Add early clobbers to some input/output asm operands arch/arm64/include/asm/atomic_lse.h | 24 ++++++++--------- arch/arm64/kernel/arm64ksyms.c | 8 ++++++ arch/arm64/lib/tishift.S | 15 ++--------- arch/arm64/mm/fault.c | 51 +++++++++++++++++++++++++++++++++++++ arch/arm64/mm/mmu.c | 16 +++++++----- 5 files changed, 83 insertions(+), 31 deletions(-)
WARNING: multiple messages have this Message-ID (diff)
From: will.deacon@arm.com (Will Deacon) To: linux-arm-kernel@lists.infradead.org Subject: [GIT PULL] arm64: fixes for -rc7 Date: Fri, 25 May 2018 17:04:49 +0100 [thread overview] Message-ID: <20180525160448.GF3255@arm.com> (raw) Hi Linus, Here are a few arm64 fixes for -rc7. The two main fixes are for the asm constraints in our LSE atomics and for our pmd/pud setters when changing permissions for kernel mappings. Summary in the tag. Please pull, Will --->8 The following changes since commit 771c577c23bac90597c685971d7297ea00f99d11: Linux 4.17-rc6 (2018-05-20 15:31:38 -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 82034c23fcbc2389c73d97737f61fa2dd6526413: arm64: Make sure permission updates happen for pmd/pud (2018-05-24 11:19:31 +0100) ---------------------------------------------------------------- More arm64 fixes: - Fix application of read-only permissions to kernel section mappings - Sanitise reported ESR values for signals delivered on a kernel address - Ensure tishift GCC helpers are exported to modules - Fix inline asm constraints for some LSE atomics ---------------------------------------------------------------- Jason A. Donenfeld (1): arm64: export tishift functions to modules Laura Abbott (1): arm64: Make sure permission updates happen for pmd/pud Peter Maydell (1): arm64: fault: Don't leak data in ESR context for user fault on kernel VA Will Deacon (1): arm64: lse: Add early clobbers to some input/output asm operands arch/arm64/include/asm/atomic_lse.h | 24 ++++++++--------- arch/arm64/kernel/arm64ksyms.c | 8 ++++++ arch/arm64/lib/tishift.S | 15 ++--------- arch/arm64/mm/fault.c | 51 +++++++++++++++++++++++++++++++++++++ arch/arm64/mm/mmu.c | 16 +++++++----- 5 files changed, 83 insertions(+), 31 deletions(-)
next reply other threads:[~2018-05-25 16:04 UTC|newest] Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-05-25 16:04 Will Deacon [this message] 2018-05-25 16:04 ` [GIT PULL] arm64: fixes for -rc7 Will Deacon -- strict thread matches above, loose matches on Subject: below -- 2022-09-23 18:28 [GIT PULL] arm64 " Will Deacon 2022-09-23 18:28 ` Will Deacon 2022-09-23 22:43 ` Linus Torvalds 2022-09-23 22:43 ` Linus Torvalds 2022-09-28 10:46 ` Mark Rutland 2022-09-28 10:46 ` Mark Rutland 2022-09-23 22:53 ` pr-tracker-bot 2022-09-23 22:53 ` pr-tracker-bot 2022-05-13 16:52 Will Deacon 2022-05-13 16:52 ` Will Deacon 2022-05-13 17:30 ` pr-tracker-bot 2022-05-13 17:30 ` pr-tracker-bot 2021-08-20 8:53 Will Deacon 2021-08-20 8:53 ` Will Deacon 2021-08-20 20:09 ` pr-tracker-bot 2021-08-20 20:09 ` pr-tracker-bot 2020-12-02 17:17 Will Deacon 2020-12-02 17:17 ` Will Deacon 2020-12-02 20:48 ` pr-tracker-bot 2020-12-02 20:48 ` pr-tracker-bot 2020-03-20 15:35 Will Deacon 2020-03-20 15:35 ` Will Deacon 2020-03-20 17:15 ` pr-tracker-bot 2020-03-20 17:15 ` pr-tracker-bot 2019-08-28 17:32 [GIT PULL] arm64: Fixes " Will Deacon 2019-08-28 17:32 ` Will Deacon 2019-08-28 17:32 ` Will Deacon 2019-08-28 17:45 ` pr-tracker-bot 2019-08-28 17:45 ` pr-tracker-bot 2019-08-28 17:45 ` pr-tracker-bot 2018-07-27 11:51 [GIT PULL] arm64: fixes " Will Deacon 2018-07-27 11:51 ` Will Deacon 2016-07-08 14:49 Will Deacon 2016-07-08 14: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=20180525160448.GF3255@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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.