From: Florian Westphal <fw@strlen.de>
To: Quentin Monnet <quentin@isovalent.com>
Cc: Florian Westphal <fw@strlen.de>,
bpf@vger.kernel.org, netdev@vger.kernel.org,
netfilter-devel@vger.kernel.org, dxu@dxuuu.xyz, qde@naccy.de
Subject: Re: [PATCH bpf-next v3 5/6] tools: bpftool: print netfilter link info
Date: Tue, 18 Apr 2023 21:50:01 +0200 [thread overview]
Message-ID: <20230418195001.GB21058@breakpoint.cc> (raw)
In-Reply-To: <b325e432-7652-96d3-055a-0107a88ea1fa@isovalent.com>
Quentin Monnet <quentin@isovalent.com> wrote:
> > + if (nf_link_count > (INT_MAX / sizeof(info))) {
> > + fprintf(stderr, "link count %d\n", nf_link_count);
>
> The only nit I have is that we could use p_err() here, and have a more
> descriptive message (letting user know that we've reached a limit).
Drats, I'll replace this and will retain your RvB tag in v4, thanks.
next prev parent reply other threads:[~2023-04-18 19:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-18 13:10 [PATCH bpf-next v3 0/6] bpf: add netfilter program type Florian Westphal
2023-04-18 13:10 ` [PATCH bpf-next v3 1/6] bpf: add bpf_link support for BPF_NETFILTER programs Florian Westphal
2023-04-18 18:35 ` Alexei Starovoitov
2023-04-18 19:48 ` Florian Westphal
2023-04-19 5:57 ` kernel test robot
2023-04-18 13:10 ` [PATCH bpf-next v3 2/6] bpf: minimal support for programs hooked into netfilter framework Florian Westphal
2023-04-19 2:11 ` Alexei Starovoitov
2023-04-18 13:10 ` [PATCH bpf-next v3 3/6] netfilter: nfnetlink hook: dump bpf prog id Florian Westphal
2023-04-20 9:54 ` Simon Horman
2023-04-18 13:10 ` [PATCH bpf-next v3 4/6] netfilter: disallow bpf hook attachment at same priority Florian Westphal
2023-04-18 13:10 ` [PATCH bpf-next v3 5/6] tools: bpftool: print netfilter link info Florian Westphal
2023-04-18 14:20 ` Quentin Monnet
2023-04-18 19:50 ` Florian Westphal [this message]
2023-04-18 13:10 ` [PATCH bpf-next v3 6/6] bpf: add test_run support for netfilter program type Florian Westphal
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=20230418195001.GB21058@breakpoint.cc \
--to=fw@strlen.de \
--cc=bpf@vger.kernel.org \
--cc=dxu@dxuuu.xyz \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=qde@naccy.de \
--cc=quentin@isovalent.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;
as well as URLs for NNTP newsgroup(s).