From: Justin Stitt <justinstitt@google.com>
To: Nathan Chancellor <nathan@kernel.org>
Cc: pablo@netfilter.org, coreteam@netfilter.org, davem@davemloft.net,
edumazet@google.com, fw@strlen.de, kadlec@netfilter.org,
kuba@kernel.org, linux-kernel@vger.kernel.org,
llvm@lists.linux.dev, ndesaulniers@google.com,
netdev@vger.kernel.org, netfilter-devel@vger.kernel.org,
pabeni@redhat.com, trix@redhat.com
Subject: Re: [PATCH] netfilter: xt_TPROXY: remove pr_debug invocations
Date: Tue, 12 Jul 2022 13:38:57 -0700 [thread overview]
Message-ID: <CAFhGd8qz_QfX-h43koOcr6bKMRvESomgF2siQtkB=7ZRxWbwvA@mail.gmail.com> (raw)
In-Reply-To: <Ys3DwnYiF9eDwr2T@dev-arch.thelio-3990X>
On Tue, Jul 12, 2022 at 11:56 AM Nathan Chancellor <nathan@kernel.org> wrote:
>
> Hi Justin,
>
> On Tue, Jul 12, 2022 at 11:34:52AM -0700, Justin Stitt wrote:
> > pr_debug calls are no longer needed in this file.
> >
> > Pablo suggested "a patch to remove these pr_debug calls". This patch has
> > some other beneficial collateral as it also silences multiple Clang
> > -Wformat warnings that were present in the pr_debug calls.
> >
> > Suggested-by: Pablo Neira Ayuso <pablo@netfilter.org>
> > Signed-off-by: Justin Stitt <justinstitt@google.com>
>
> Thanks for the patch!
>
> Reviewed-by: Nathan Chancellor <nathan@kernel.org>
>
> Couple of style comments below that probably warrant a v2, you can carry
> the above tag forward for future revisions. No need to give me a
> "Suggested-by".
>
> > ---
> > Suggestion here: https://lore.kernel.org/all/Ys0zZACWwGilTwHx@salvia/
> >
> > net/netfilter/xt_TPROXY.c | 19 -------------------
> > 1 file changed, 19 deletions(-)
> >
> > diff --git a/net/netfilter/xt_TPROXY.c b/net/netfilter/xt_TPROXY.c
> > index 459d0696c91a..dc7284e6357b 100644
> > --- a/net/netfilter/xt_TPROXY.c
> > +++ b/net/netfilter/xt_TPROXY.c
> > @@ -74,18 +74,10 @@ tproxy_tg4(struct net *net, struct sk_buff *skb, __be32 laddr, __be16 lport,
> > /* This should be in a separate target, but we don't do multiple
> > targets on the same rule yet */
> > skb->mark = (skb->mark & ~mark_mask) ^ mark_value;
> > -
> > - pr_debug("redirecting: proto %hhu %pI4:%hu -> %pI4:%hu, mark: %x\n",
> > - iph->protocol, &iph->daddr, ntohs(hp->dest),
> > - &laddr, ntohs(lport), skb->mark);
> > -
> > nf_tproxy_assign_sock(skb, sk);
> > return NF_ACCEPT;
> > }
> >
> > - pr_debug("no socket, dropping: proto %hhu %pI4:%hu -> %pI4:%hu, mark: %x\n",
> > - iph->protocol, &iph->saddr, ntohs(hp->source),
> > - &iph->daddr, ntohs(hp->dest), skb->mark);
> > return NF_DROP;
> > }
> >
> > @@ -123,13 +115,11 @@ tproxy_tg6_v1(struct sk_buff *skb, const struct xt_action_param *par)
> >
> > tproto = ipv6_find_hdr(skb, &thoff, -1, NULL, NULL);
> > if (tproto < 0) {
>
> checkpatch.pl should have warned that these if statement braces here and
> below are no longer necessary because there is only one statement within
> them now.
Weirdly, checkpatch.pl gave 0 warnings regarding this patch. At any
rate, v2 is coming shortly. Thanks for the review!
>
> if (tproto < 0)
> return NF_DROP;
>
> I believe it is important to do these types of style cleanups when doing
> a larger change so that people do not try to do them as standalone
> changes, which can irritate maintainers.
>
> > - pr_debug("unable to find transport header in IPv6 packet, dropping\n");
> > return NF_DROP;
> > }
> >
> > hp = skb_header_pointer(skb, thoff, sizeof(_hdr), &_hdr);
> > if (hp == NULL) {
> > - pr_debug("unable to grab transport header contents in IPv6 packet, dropping\n");
> > return NF_DROP;
> > }
>
> if (hp == NULL)
> return NF_DROP;
>
> could even go a step farther and make it
>
> if (!hp)
> return NF_DROP;
>
> if there is a warning about that.
>
> >
> > @@ -168,19 +158,10 @@ tproxy_tg6_v1(struct sk_buff *skb, const struct xt_action_param *par)
> > /* This should be in a separate target, but we don't do multiple
> > targets on the same rule yet */
> > skb->mark = (skb->mark & ~tgi->mark_mask) ^ tgi->mark_value;
> > -
> > - pr_debug("redirecting: proto %hhu %pI6:%hu -> %pI6:%hu, mark: %x\n",
> > - tproto, &iph->saddr, ntohs(hp->source),
> > - laddr, ntohs(lport), skb->mark);
> > -
> > nf_tproxy_assign_sock(skb, sk);
> > return NF_ACCEPT;
> > }
> >
> > - pr_debug("no socket, dropping: proto %hhu %pI6:%hu -> %pI6:%hu, mark: %x\n",
> > - tproto, &iph->saddr, ntohs(hp->source),
> > - &iph->daddr, ntohs(hp->dest), skb->mark);
> > -
> > return NF_DROP;
> > }
> >
> > --
> > 2.37.0.144.g8ac04bfd2-goog
> >
next prev parent reply other threads:[~2022-07-12 20:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-07 19:17 [PATCH] netfilter: xt_TPROXY: fix clang -Wformat warnings: Justin Stitt
2022-07-08 23:33 ` Nick Desaulniers
2022-07-11 9:04 ` Pablo Neira Ayuso
2022-07-11 19:44 ` Justin Stitt
2022-07-12 8:40 ` Pablo Neira Ayuso
2022-07-12 18:34 ` [PATCH] netfilter: xt_TPROXY: remove pr_debug invocations Justin Stitt
2022-07-12 18:56 ` Nathan Chancellor
2022-07-12 20:38 ` Justin Stitt [this message]
2022-07-12 20:49 ` [PATCH v2] " Justin Stitt
2022-07-18 17:43 ` Justin Stitt
2022-07-18 21:38 ` Pablo Neira Ayuso
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='CAFhGd8qz_QfX-h43koOcr6bKMRvESomgF2siQtkB=7ZRxWbwvA@mail.gmail.com' \
--to=justinstitt@google.com \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=kadlec@netfilter.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pablo@netfilter.org \
--cc=trix@redhat.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).