From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: <jiang.peng9@zte.com.cn>
Cc: <naveen@kernel.org>, <anil.s.keshavamurthy@intel.com>,
<davem@davemloft.net>, <mhiramat@kernel.org>,
<linux-kernel@vger.kernel.org>,
<linux-trace-kernel@vger.kernel.org>, <xu.xin16@zte.com.cn>,
<yang.yang29@zte.com.cn>
Subject: Re: [PATCH] kprobes: Add missing kerneldoc for __get_insn_slot
Date: Tue, 15 Jul 2025 09:54:17 +0900 [thread overview]
Message-ID: <20250715095417.a14bed2f6437bb0545fa163c@kernel.org> (raw)
In-Reply-To: <20250704143817707TOCcfTRWsO5OAbQ2eYoU9@zte.com.cn>
On Fri, 4 Jul 2025 14:38:17 +0800 (CST)
<jiang.peng9@zte.com.cn> wrote:
> From: Peng Jiang <jiang.peng9@zte.com.cn>
>
> Add kerneldoc for '__get_insn_slot' function to fix W=1 warnings:
>
> kernel/kprobes.c:141 function parameter 'c' not described in '__get_insn_slot'
>
Good catch! Let me pick it for-next.
Thanks!
> Signed-off-by: Peng Jiang <jiang.peng9@zte.com.cn>
> ---
> kernel/kprobes.c | 8 ++++++--
> 1 file changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/kernel/kprobes.c b/kernel/kprobes.c
> index ffe0c3d52306..ab8f9fc1f0d1 100644
> --- a/kernel/kprobes.c
> +++ b/kernel/kprobes.c
> @@ -135,8 +135,12 @@ struct kprobe_insn_cache kprobe_insn_slots = {
> static int collect_garbage_slots(struct kprobe_insn_cache *c);
>
> /**
> - * __get_insn_slot() - Find a slot on an executable page for an instruction.
> - * We allocate an executable page if there's no room on existing ones.
> + * __get_insn_slot - Find a slot on an executable page for an instruction.
> + * @c: Pointer to kprobe instruction cache
> + *
> + * Description: Locates available slot on existing executable pages,
> + * allocates an executable page if there's no room on existing ones.
> + * Return: Pointer to instruction slot on success, NULL on failure.
> */
> kprobe_opcode_t *__get_insn_slot(struct kprobe_insn_cache *c)
> {
> --
> 2.25.1
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
prev parent reply other threads:[~2025-07-15 0:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-04 6:38 jiang.peng9
2025-07-15 0:54 ` Masami Hiramatsu [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=20250715095417.a14bed2f6437bb0545fa163c@kernel.org \
--to=mhiramat@kernel.org \
--cc=anil.s.keshavamurthy@intel.com \
--cc=davem@davemloft.net \
--cc=jiang.peng9@zte.com.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=naveen@kernel.org \
--cc=xu.xin16@zte.com.cn \
--cc=yang.yang29@zte.com.cn \
/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
all inboxes | Powered by JetHome®