[PATCH v7 4/8] bpftool: Ensure task comm is always NUL-terminated
Alejandro Colomar
alx at kernel.org
Sat Aug 17 08:38:58 UTC 2024
Hi Yafang,
On Sat, Aug 17, 2024 at 10:56:20AM GMT, Yafang Shao wrote:
> Let's explicitly ensure the destination string is NUL-terminated. This way,
> it won't be affected by changes to the source string.
>
> Signed-off-by: Yafang Shao <laoar.shao at gmail.com>
> Reviewed-by: Quentin Monnet <qmo at kernel.org>
> ---
> tools/bpf/bpftool/pids.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/tools/bpf/bpftool/pids.c b/tools/bpf/bpftool/pids.c
> index 9b898571b49e..23f488cf1740 100644
> --- a/tools/bpf/bpftool/pids.c
> +++ b/tools/bpf/bpftool/pids.c
> @@ -54,6 +54,7 @@ static void add_ref(struct hashmap *map, struct pid_iter_entry *e)
> ref = &refs->refs[refs->ref_cnt];
> ref->pid = e->pid;
> memcpy(ref->comm, e->comm, sizeof(ref->comm));
> + ref->comm[sizeof(ref->comm) - 1] = '\0';
Why doesn't this use strscpy()? Isn't the source terminated?
Both the source and the destination measure 16 characters. If it is
true that the source is not terminated, then this copy might truncate
the (non-)string by overwriting the last byte with a NUL. Is that
truncation a good thing?
> refs->ref_cnt++;
>
> return;
> @@ -77,6 +78,7 @@ static void add_ref(struct hashmap *map, struct pid_iter_entry *e)
> ref = &refs->refs[0];
> ref->pid = e->pid;
> memcpy(ref->comm, e->comm, sizeof(ref->comm));
> + ref->comm[sizeof(ref->comm) - 1] = '\0';
Same question here.
> refs->ref_cnt = 1;
> refs->has_bpf_cookie = e->has_bpf_cookie;
> refs->bpf_cookie = e->bpf_cookie;
> --
> 2.43.5
>
--
<https://www.alejandro-colomar.es/>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20240817/291e6400/attachment.sig>
More information about the dri-devel
mailing list