From: Vladimir Kondratiev <Vladimir.Kondratiev@mobileye.com>
To: Guo Ren <guoren@kernel.org>
Cc: "Paul Walmsley" <pjw@kernel.org>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Albert Ou" <aou@eecs.berkeley.edu>,
"Alexandre Ghiti" <alex@ghiti.fr>,
"Masami Hiramatsu" <mhiramat@kernel.org>,
"Oleg Nesterov" <oleg@redhat.com>,
"Peter Zijlstra" <peterz@infradead.org>,
"Pekka Enberg" <penberg@kernel.org>,
"Patrick Stählin" <me@packi.ch>,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org,
"Palmer Dabbelt" <palmerdabbelt@google.com>
Subject: Re: [PATCH v3 2/2] riscv: probes: reject probes inside an LR/SC sequence
Date: Sun, 15 Nov 2026 09:17:28 +0200 [thread overview]
Message-ID: <cd92fe07-9a9b-4a21-b596-1b2d007b4c9f@mobileye.com> (raw)
In-Reply-To: <CAJF2gTTY5ODDH6XV2h1v+T7Sn5BK3L9x-Q_Qb_EXNmdCor5rPA@mail.gmail.com>
On 11/13/26 10:01, Guo Ren wrote:
>> Fixes: c22b0bcb1dd0 ("riscv: Add kprobes supported")
>> Fixes: 74784081aac8 ("riscv: Add uprobes supported")
> One patch for one Fixes tag, is that okay?
One for kprobes, 2-nd for uprobes. This is what sashiko-bot suggested, I
thought it knows the policy better than me. If it should be different,
just let me know.
Thanks, Vladimir
prev parent reply other threads:[~2026-11-15 7:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-12 10:01 [PATCH v3 0/2] riscv: probes: reject probes inside an LR/SC sequence Vladimir Kondratiev
2026-11-12 10:01 ` [PATCH v3 1/2] riscv: kprobes: fix out-of-bounds read in riscv_probe_decode_insn Vladimir Kondratiev
2026-11-13 7:53 ` Guo Ren
2026-11-12 10:01 ` [PATCH v3 2/2] riscv: probes: reject probes inside an LR/SC sequence Vladimir Kondratiev
2026-11-13 8:01 ` Guo Ren
2026-11-15 7:17 ` Vladimir Kondratiev [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=cd92fe07-9a9b-4a21-b596-1b2d007b4c9f@mobileye.com \
--to=vladimir.kondratiev@mobileye.com \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=guoren@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=me@packi.ch \
--cc=mhiramat@kernel.org \
--cc=oleg@redhat.com \
--cc=palmer@dabbelt.com \
--cc=palmerdabbelt@google.com \
--cc=penberg@kernel.org \
--cc=peterz@infradead.org \
--cc=pjw@kernel.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