Re: [PATCH bpf-next v5 2/3] bpf: implement dynptr copy kfuncs

[Alexei Starovoitov <alexei.starovoitov@xxxxxxxxx>]

On Mon, May 12, 2025 at 1:53 PM Mykyta Yatsenko
<mykyta.yatsenko5@xxxxxxxxx> wrote:
>
>
> +typedef int (*copy_fn_t)(void *dst, const void *src, u32 size, struct task_struct *tsk);
> +
> +/* The __always_inline is to make sure the compiler doesn't

moved it to new line as:
/*
 * The __always_inline is to make sure the compiler doesn't

Please use the kernel coding style instead of the old networking
style from now on.


> + * generate indirect calls into callbacks, which is expensive,
> + * on some kernel configurations. This allows compiler to put
> + * direct calls into all the specific callback implementations
> + *(copy_user_data_sleepable, copy_user_data_nofault, and so on)

Added extra space after *

> + */

while applying.