From: patchwork-bot+linux-riscv@kernel.org
To: Conor Dooley <conor.dooley@microchip.com>
Cc: linux-riscv@lists.infradead.org, palmer@dabbelt.com,
palmerdabbelt@google.com, changbin.du@huawei.com,
rostedt@goodmis.org, changbin.du@gmail.com, palmer@rivosinc.com
Subject: Re: [PATCH v5] RISC-V: Don't check text_mutex during stop_machine
Date: Fri, 10 Mar 2023 02:30:19 +0000 [thread overview]
Message-ID: <167841541915.17842.2873145112302800461.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230303143754.4005217-1-conor.dooley@microchip.com>
Hello:
This patch was applied to riscv/linux.git (fixes)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Fri, 3 Mar 2023 14:37:55 +0000 you wrote:
> From: Palmer Dabbelt <palmerdabbelt@google.com>
>
> We're currently using stop_machine() to update ftrace & kprobes, which
> means that the thread that takes text_mutex during may not be the same
> as the thread that eventually patches the code. This isn't actually a
> race because the lock is still held (preventing any other concurrent
> accesses) and there is only one thread running during stop_machine(),
> but it does trigger a lockdep failure.
>
> [...]
Here is the summary with links:
- [v5] RISC-V: Don't check text_mutex during stop_machine
https://git.kernel.org/riscv/c/2a8db5ec4a28
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-03-10 2:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-03 14:37 [PATCH v5] RISC-V: Don't check text_mutex during stop_machine Conor Dooley
2023-03-10 2:30 ` 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=167841541915.17842.2873145112302800461.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=changbin.du@gmail.com \
--cc=changbin.du@huawei.com \
--cc=conor.dooley@microchip.com \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=palmer@rivosinc.com \
--cc=palmerdabbelt@google.com \
--cc=rostedt@goodmis.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