Re: [PATCH v2] lkdtm: mark lkdtm_kprobe_handler for kprobe unavailable

[Greg KH <gregkh@linuxfoundation.org>]

On Tue, Aug 27, 2024 at 08:07:36PM +0800, Xianting Tian wrote:
> Signed-off-by: Xianting Tian <xianting.tian@linux.alibaba.com>
> ---
>  drivers/misc/lkdtm/core.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/misc/lkdtm/core.c b/drivers/misc/lkdtm/core.c
> index 5732fd59a227..b32b18f498ea 100644
> --- a/drivers/misc/lkdtm/core.c
> +++ b/drivers/misc/lkdtm/core.c
> @@ -223,6 +223,7 @@ static int lkdtm_kprobe_handler(struct kprobe *kp, struct pt_regs *regs)
>  
>  	return 0;
>  }
> +NOKPROBE_SYMBOL(lkdtm_kprobe_handler);
>  
>  static ssize_t lkdtm_debugfs_entry(struct file *f,
>  				   const char __user *user_buf,
> -- 
> 2.43.5
> 

Hi,

This is the friendly patch-bot of Greg Kroah-Hartman.  You have sent him
a patch that has triggered this response.  He used to manually respond
to these common problems, but in order to save his sanity (he kept
writing the same thing over and over, yet to different people), I was
created.  Hopefully you will not take offence and will fix the problem
in your patch and resubmit it so that it can be accepted into the Linux
kernel tree.

You are receiving this message because of the following common error(s)
as indicated below:

- Your patch contains warnings and/or errors noticed by the
  scripts/checkpatch.pl tool.

- You did not specify a description of why the patch is needed, or
  possibly, any description at all, in the email body.  Please read the
  section entitled "The canonical patch format" in the kernel file,
  Documentation/process/submitting-patches.rst for what is needed in
  order to properly describe the change.

- This looks like a new version of a previously submitted patch, but you
  did not list below the --- line any changes from the previous version.
  Please read the section entitled "The canonical patch format" in the
  kernel file, Documentation/process/submitting-patches.rst for what
  needs to be done here to properly describe this.

If you wish to discuss this problem further, or you have questions about
how to resolve this issue, please feel free to respond to this email and
Greg will reply once he has dug out from the pending patches received
from other developers.

thanks,

greg k-h's patch email bot