linux-kernel - Re: [PATCH] selftests/bpf: Fix incorrect parameters in NULL pointer checking

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <58f57d70-a787-4012-8763-cc6eb642ef8a@stanley.mountain>
Date: Thu, 22 Aug 2024 00:50:16 +0300
From: Dan Carpenter <dan.carpenter@...aro.org>
To: Yonghong Song <yonghong.song@...ux.dev>
Cc: Hao Ge <hao.ge@...ux.dev>, ast@...nel.org, daniel@...earbox.net,
	andrii@...nel.org, martin.lau@...ux.dev, eddyz87@...il.com,
	song@...nel.org, john.fastabend@...il.com, kpsingh@...nel.org,
	sdf@...ichev.me, haoluo@...gle.com, jolsa@...nel.org,
	mykolal@...com, shuah@...nel.org, bpf@...r.kernel.org,
	linux-kselftest@...r.kernel.org, linux-kernel@...r.kernel.org,
	Hao Ge <gehao@...inos.cn>
Subject: Re: [PATCH] selftests/bpf: Fix incorrect parameters in NULL pointer
 checking

On Wed, Aug 21, 2024 at 02:03:17PM -0700, Yonghong Song wrote:
> 
> On 8/19/24 7:34 PM, Hao Ge wrote:
> > From: Hao Ge <gehao@...inos.cn>
> > 
> > Smatch reported the following warning:
> >      ./tools/testing/selftests/bpf/testing_helpers.c:455 get_xlated_program()
> >      warn: variable dereferenced before check 'buf' (see line 454)
> > 
> > It seems correct,so let's modify it based on it's suggestion.
> > 
> > Actually,commit b23ed4d74c4d ("selftests/bpf: Fix invalid pointer
> > check in get_xlated_program()") fixed an issue in the test_verifier.c
> > once,but it was reverted this time.
> > 
> > Let's solve this issue with the minimal changes possible.
> > 
> > Reported-by: Dan Carpenter <dan.carpenter@...aro.org>
> > Closes: https://lore.kernel.org/all/1eb3732f-605a-479d-ba64-cd14250cbf91@stanley.mountain/
> > Fixes: b4b7a4099b8c ("selftests/bpf: Factor out get_xlated_program() helper")
> > Signed-off-by: Hao Ge <gehao@...inos.cn>
> 
> In the future, please change subject '[PATCH] ...' to '[PATCH bpf-next] ...'
> so CI can properly test it.

It feels like there should be a technical solution to this.  The CI system is
something on AWS and it's too expensive to just check every patch that's sent to
the bpf list?  My understanding is that there are only two bpf trees.

	if [ "$FIXES_HASH" == "" ] ; then
		TREE=next
	elif git merge-base --is-ancestor $FIXES_HASH origin/master ; then
		TREE=linus
	else
		TREE=next
	fi

These days the zero day bot people are checking around a thousand git trees.
They pull emails off the various lists and apply them to the right places.  It's
a doable thing.

regards,
dan carpenter