From: Kui-Feng Lee <sinquersw@gmail.com>
To: Dan Carpenter <dan.carpenter@linaro.org>
Cc: thinker.li@gmail.com, bpf@vger.kernel.org
Subject: Re: [bug report] selftests/bpf: Verify that the cgroup_skb filters receive expected packets.
Date: Fri, 4 Aug 2023 10:32:13 -0700 [thread overview]
Message-ID: <0efe1e4d-fd1f-4841-862f-8686ef366c40@gmail.com> (raw)
In-Reply-To: <d52eeb7b-55b3-4696-83bc-4d64f2853dfe@kadam.mountain>
On 8/3/23 22:13, Dan Carpenter wrote:
> On Thu, Aug 03, 2023 at 01:43:33PM -0700, Kui-Feng Lee wrote:
>>>> 113 int err;
>>>> 114
>>>> 115 addr.sin6_port = htons(get_sock_port_v6(listen_fd));
>>>> --> 116 if (addr.sin6_port < 0)
>>>> ^^^^^^^^^^^^^^^^^^
>>>> Impossible and also it doesn't make sense to compare network endian data
>>>> with < 0.
>>>
>>> Hi Dan,
>>>
>>> Thank you for pointing it out. It should check the returned value
>>> of get_sock_port_v6() before calling htons(). I will send a patch
>>> to fix it asap.
>>
>> Could you show me how to run Smatch againt bpf selftests?
>>
>
> Oh wow... You don't want to know. So sometimes I'll go through and
> do a `find -name \*.c` and if there isn't a matching .o file I'll just
> run:
>
> ~/path/to/smatch tools/testing/selftests/bpf/prog_tests/cgroup_tcp_skb.c
>
> Smatch has a thing where if the .h file is missing it will just include
> the nearest .h file with a similar name. This doesn't work well and
> generates a ton of errors. But I grep the output for specific types
> of errors like "is never less than zero".
Got it! Thanks!
>
> regards,
> dan carpenter
>
prev parent reply other threads:[~2023-08-04 17:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-31 7:27 [bug report] selftests/bpf: Verify that the cgroup_skb filters receive expected packets Dan Carpenter
2023-08-03 19:52 ` Kui-Feng Lee
2023-08-03 20:43 ` Kui-Feng Lee
2023-08-04 5:13 ` Dan Carpenter
2023-08-04 17:32 ` Kui-Feng Lee [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=0efe1e4d-fd1f-4841-862f-8686ef366c40@gmail.com \
--to=sinquersw@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=dan.carpenter@linaro.org \
--cc=thinker.li@gmail.com \
/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