From: Palmer Dabbelt <palmer@dabbelt.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] RISC-V Fixes for 5.8-rc2
Date: Fri, 19 Jun 2020 16:24:29 -0700 (PDT) [thread overview]
Message-ID: <mhng-ff59c9fd-a367-4804-bc35-73c8a572b016@palmerdabbelt-glaptop1> (raw)
The following changes since commit cd16ed33c3c618930ccda7049dcea05ee707a9c0:
Merge tag 'riscv-for-linus-5.8-mw1' of git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux (2020-06-11 12:55:20 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git tags/riscv-for-linus-5.8-rc2
for you to fetch changes up to 0e2c09011d4de4161f615ff860a605a9186cf62a:
RISC-V: Acquire mmap lock before invoking walk_page_range (2020-06-18 18:46:09 -0700)
----------------------------------------------------------------
RISC-V Fixes for 5.8-rc2
This contains three fixes that I'd like to target for rc2:
* A workaround for a compiler surprise related to the "r" inline assembly that
allows LLVM to boot.
* A fix to avoid WX-only mappings, which the ISA does not allow. While this
probably manifests in many ways, the bug was found in stress-ng.
* A missing lock in set_direct_map_*(), which due to a recent lockdep change
started asserting.
----------------------------------------------------------------
Atish Patra (1):
RISC-V: Acquire mmap lock before invoking walk_page_range
Nathan Huckleberry (1):
riscv/atomic: Fix sign extension for RV64I
Yash Shah (1):
RISC-V: Don't allow write+exec only page mapping request in mmap
arch/riscv/include/asm/cmpxchg.h | 8 ++++----
arch/riscv/kernel/sys_riscv.c | 6 ++++++
arch/riscv/mm/pageattr.c | 14 ++++++++++++--
3 files changed, 22 insertions(+), 6 deletions(-)
next reply other threads:[~2020-06-19 23:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-19 23:24 Palmer Dabbelt [this message]
2020-06-20 19:55 ` [GIT PULL] RISC-V Fixes for 5.8-rc2 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=mhng-ff59c9fd-a367-4804-bc35-73c8a572b016@palmerdabbelt-glaptop1 \
--to=palmer@dabbelt.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).