From: patchwork-bot+linux-riscv@kernel.org
To: Alexandre Ghiti <alexghiti@rivosinc.com>
Cc: linux-riscv@lists.infradead.org, paul.walmsley@sifive.com,
palmer@dabbelt.com, aou@eecs.berkeley.edu,
vincent.chen@sifive.com, zong.li@sifive.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH -fixes 0/2] Fix WX mappings in the linear mapping after module unloading
Date: Thu, 21 Dec 2023 03:00:24 +0000 [thread overview]
Message-ID: <170312762431.27922.8717451486214293003.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231213134027.155327-1-alexghiti@rivosinc.com>
Hello:
This series was applied to riscv/linux.git (fixes)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Wed, 13 Dec 2023 14:40:25 +0100 you wrote:
> I fell onto a bunch of WX mappings in the linear mapping after a module
> gets unloaded, this is because our module_alloc() does not set the
> VM_FLUSH_RESET_PERMS flag (patch 1) and that
> set_direct_map_default_noflush() must clean the X bit (patch 2).
>
> Note that the Fixes tags are correct but patch 2 will fail to apply
> since a change in this function just landed in 6.7.
>
> [...]
Here is the summary with links:
- [-fixes,1/2] riscv: Fix module_alloc() that did not reset the linear mapping permissions
https://git.kernel.org/riscv/c/2f748fa7b60a
- [-fixes,2/2] riscv: Fix set_direct_map_default_noflush() to reset _PAGE_EXEC
https://git.kernel.org/riscv/c/3b5c14361d61
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2023-12-21 3:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-13 13:40 [PATCH -fixes 0/2] Fix WX mappings in the linear mapping after module unloading Alexandre Ghiti
2023-12-13 13:40 ` [PATCH -fixes 1/2] riscv: Fix module_alloc() that did not reset the linear mapping permissions Alexandre Ghiti
2023-12-13 13:40 ` [PATCH -fixes 2/2] riscv: Fix set_direct_map_default_noflush() to reset _PAGE_EXEC Alexandre Ghiti
2023-12-21 3:00 ` patchwork-bot+linux-riscv [this message]
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=170312762431.27922.8717451486214293003.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=alexghiti@rivosinc.com \
--cc=aou@eecs.berkeley.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=vincent.chen@sifive.com \
--cc=zong.li@sifive.com \
/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