From: Liao Chang <liaochang1@huawei.com> To: <paul.walmsley@sifive.com>, <palmer@dabbelt.com>, <aou@eecs.berkeley.edu>, <mhiramat@kernel.org>, <rostedt@goodmis.org>, <peterz@infradead.org>, <jszhang@kernel.org>, <liaochang1@huawei.com>, <naveen.n.rao@linux.vnet.ibm.com> Cc: <linux-riscv@lists.infradead.org>, <linux-kernel@vger.kernel.org> Subject: [PATCH] riscv/kprobe: reclaim insn_slot on kprobe unregistration Date: Mon, 23 May 2022 09:51:24 +0800 [thread overview] Message-ID: <20220523015124.98743-1-liaochang1@huawei.com> (raw) On kprobe registration kernel allocate one insn_slot for new kprobe, but it forget to reclaim the insn_slot on unregistration, leading to a potential leakage. This bug reported by Chen Guokai <chenguokai17@mails.ucas.ac.cn>. Signed-off-by: Liao Chang <liaochang1@huawei.com> --- arch/riscv/kernel/probes/kprobes.c | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/arch/riscv/kernel/probes/kprobes.c b/arch/riscv/kernel/probes/kprobes.c index e6e950b7cf32..f12eb1fbb52c 100644 --- a/arch/riscv/kernel/probes/kprobes.c +++ b/arch/riscv/kernel/probes/kprobes.c @@ -110,6 +110,10 @@ void __kprobes arch_disarm_kprobe(struct kprobe *p) void __kprobes arch_remove_kprobe(struct kprobe *p) { + if (p->ainsn.api.insn) { + free_insn_slot(p->ainsn.api.insn, 0); + p->ainsn.api.insn = NULL; + } } static void __kprobes save_previous_kprobe(struct kprobe_ctlblk *kcb) -- 2.17.1
WARNING: multiple messages have this Message-ID (diff)
From: Liao Chang <liaochang1@huawei.com> To: <paul.walmsley@sifive.com>, <palmer@dabbelt.com>, <aou@eecs.berkeley.edu>, <mhiramat@kernel.org>, <rostedt@goodmis.org>, <peterz@infradead.org>, <jszhang@kernel.org>, <liaochang1@huawei.com>, <naveen.n.rao@linux.vnet.ibm.com> Cc: <linux-riscv@lists.infradead.org>, <linux-kernel@vger.kernel.org> Subject: [PATCH] riscv/kprobe: reclaim insn_slot on kprobe unregistration Date: Mon, 23 May 2022 09:51:24 +0800 [thread overview] Message-ID: <20220523015124.98743-1-liaochang1@huawei.com> (raw) On kprobe registration kernel allocate one insn_slot for new kprobe, but it forget to reclaim the insn_slot on unregistration, leading to a potential leakage. This bug reported by Chen Guokai <chenguokai17@mails.ucas.ac.cn>. Signed-off-by: Liao Chang <liaochang1@huawei.com> --- arch/riscv/kernel/probes/kprobes.c | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/arch/riscv/kernel/probes/kprobes.c b/arch/riscv/kernel/probes/kprobes.c index e6e950b7cf32..f12eb1fbb52c 100644 --- a/arch/riscv/kernel/probes/kprobes.c +++ b/arch/riscv/kernel/probes/kprobes.c @@ -110,6 +110,10 @@ void __kprobes arch_disarm_kprobe(struct kprobe *p) void __kprobes arch_remove_kprobe(struct kprobe *p) { + if (p->ainsn.api.insn) { + free_insn_slot(p->ainsn.api.insn, 0); + p->ainsn.api.insn = NULL; + } } static void __kprobes save_previous_kprobe(struct kprobe_ctlblk *kcb) -- 2.17.1 _______________________________________________ linux-riscv mailing list linux-riscv@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2022-05-23 1:53 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-23 1:51 Liao Chang [this message] 2022-05-23 1:51 ` [PATCH] riscv/kprobe: reclaim insn_slot on kprobe unregistration Liao Chang 2022-05-24 15:12 ` Jisheng Zhang 2022-05-24 15:12 ` Jisheng Zhang 2022-05-25 1:24 ` liaochang (A) 2022-05-25 1:24 ` liaochang (A)
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=20220523015124.98743-1-liaochang1@huawei.com \ --to=liaochang1@huawei.com \ --cc=aou@eecs.berkeley.edu \ --cc=jszhang@kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-riscv@lists.infradead.org \ --cc=mhiramat@kernel.org \ --cc=naveen.n.rao@linux.vnet.ibm.com \ --cc=palmer@dabbelt.com \ --cc=paul.walmsley@sifive.com \ --cc=peterz@infradead.org \ --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: 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.