public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Quentin Monnet <qmo@kernel.org>
To: Kuan-Wei Chiu <visitorckw@gmail.com>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
	martin.lau@linux.dev, eddyz87@gmail.com, song@kernel.org,
	yonghong.song@linux.dev, john.fastabend@gmail.com,
	kpsingh@kernel.org, sdf@fomichev.me, haoluo@google.com,
	jolsa@kernel.org, bpf@vger.kernel.org,
	linux-kernel@vger.kernel.org, jserv@ccns.ncku.edu.tw
Subject: Re: [PATCH] bpftool: Fix undefined behavior in qsort(NULL, 0, ...)
Date: Tue, 10 Sep 2024 15:47:34 +0100	[thread overview]
Message-ID: <c18fefbb-b22f-475f-9912-63162bf84765@kernel.org> (raw)
In-Reply-To: <20240910125826.3172950-1-visitorckw@gmail.com>

2024-09-10 20:58 UTC+0800 ~ Kuan-Wei Chiu <visitorckw@gmail.com>
> When netfilter has no entry to display, qsort is called with
> qsort(NULL, 0, ...). This results in undefined behavior, as UBSan
> reports:
> 
> net.c:827:2: runtime error: null pointer passed as argument 1, which is declared to never be null
> 
> Although the C standard does not explicitly state whether calling qsort
> with a NULL pointer when the size is 0 constitutes undefined behavior,
> Section 7.1.4 of the C standard (Use of library functions) mentions:
> 
> "Each of the following statements applies unless explicitly stated
> otherwise in the detailed descriptions that follow: If an argument to a
> function has an invalid value (such as a value outside the domain of
> the function, or a pointer outside the address space of the program, or
> a null pointer, or a pointer to non-modifiable storage when the
> corresponding parameter is not const-qualified) or a type (after
> promotion) not expected by a function with variable number of
> arguments, the behavior is undefined."
> 
> To avoid this, add an early return when nf_link_count is 0 to prevent
> calling qsort with a NULL pointer.
> 
> Signed-off-by: Kuan-Wei Chiu <visitorckw@gmail.com>
> ---
>   tools/bpf/bpftool/net.c | 3 +++
>   1 file changed, 3 insertions(+)
> 
> diff --git a/tools/bpf/bpftool/net.c b/tools/bpf/bpftool/net.c
> index 968714b4c3d4..13e098fa295a 100644
> --- a/tools/bpf/bpftool/net.c
> +++ b/tools/bpf/bpftool/net.c
> @@ -824,6 +824,9 @@ static void show_link_netfilter(void)
>   		nf_link_count++;
>   	}
>   
> +	if (!nf_link_count)
> +		return;
> +
>   	qsort(nf_link_info, nf_link_count, sizeof(*nf_link_info), netfilter_link_compar);

Thanks! As the issue is calling qsort() with a NULL pointer, could you 
please make the check on nf_link_info rather than nf_link_count? I'd 
find it easier to follow.

Quentin

      reply	other threads:[~2024-09-10 14:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-10 12:58 [PATCH] bpftool: Fix undefined behavior in qsort(NULL, 0, ...) Kuan-Wei Chiu
2024-09-10 14:47 ` Quentin Monnet [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=c18fefbb-b22f-475f-9912-63162bf84765@kernel.org \
    --to=qmo@kernel.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=haoluo@google.com \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=jserv@ccns.ncku.edu.tw \
    --cc=kpsingh@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=sdf@fomichev.me \
    --cc=song@kernel.org \
    --cc=visitorckw@gmail.com \
    --cc=yonghong.song@linux.dev \
    /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