From: Joe Perches <joe@perches.com>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netdev@vger.kernel.org, davem@davemloft.net,
netfilter-devel@vger.kernel.org
Subject: Re: [PATCH 7/7] netfilter: nf_ct_helper: better logging for dropped packets
Date: Mon, 18 Feb 2013 17:23:37 -0800 [thread overview]
Message-ID: <1361237017.2046.9.camel@joe-AO722> (raw)
In-Reply-To: <20130219011109.GA6362@localhost>
On Tue, 2013-02-19 at 02:11 +0100, Pablo Neira Ayuso wrote:
> On Mon, Feb 18, 2013 at 04:22:02PM -0800, Joe Perches wrote:
> > On Tue, 2013-02-19 at 01:10 +0100, pablo@netfilter.org wrote:
> > > This patch modifies the existing code to provide more specific
> > > error message in the scope of each helper to help users to debug
> > > the reason why the packet has been dropped, ie:
> > []
> > > diff --git a/include/net/netfilter/nf_conntrack_helper.h b/include/net/netfilter/nf_conntrack_helper.h
> > []
[]
> > do please try to avoid splitting formats
> >
> > nf_ct_helper_log(skb, ct,
> > "cannot add expectation");
>
> Done whenever possible, sometimes I see myself forced to split them to
> fit 80-chars per column.
It's always possible.
Just ignore line length limitations for formats.
If the formats are on a separate line, checkpatch
won't complain either.
If nf_cg_helper_log was named nf_cg_helper_printk
checkpatch wouldn't complain if the original line
with format was > 80 cols
nf_ct_helper_printk(skb, ct, "some really long format past 80 cols ...");
but then the log isn't really a printk either and
that's a checkpatch limitation on understanding
what is and isn't a logging output function.
next prev parent reply other threads:[~2013-02-19 1:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-19 0:10 [PATCH 0/7] netfilter updates for net-next pablo
2013-02-19 0:10 ` [PATCH 1/7] netfilter: fix missing dependencies for NETFILTER_XT_MATCH_CONNLABEL pablo
2013-02-19 0:10 ` [PATCH 2/7] netfilter: xt_conntrack: Add flag to support aliases pablo
2013-02-19 0:10 ` [PATCH 3/7] netfilter: xt_CT: merge common code of revision 0 and 1 pablo
2013-02-19 0:10 ` [PATCH 4/7] netfilter: xt_CT: add alias flag pablo
2013-02-19 0:10 ` [PATCH 5/7] netfilter: nfnetlink: add mutex per subsystem pablo
2013-02-19 0:10 ` [PATCH 6/7] netfilter: nf_ct_pptp: Fix comment referring to incorrect RFC pablo
2013-02-19 0:10 ` [PATCH 7/7] netfilter: nf_ct_helper: better logging for dropped packets pablo
2013-02-19 0:22 ` Joe Perches
2013-02-19 1:11 ` Pablo Neira Ayuso
2013-02-19 1:23 ` Joe Perches [this message]
2013-02-19 1:43 ` Pablo Neira Ayuso
2013-02-19 1:33 ` Joe Perches
2013-02-19 1:50 ` Pablo Neira Ayuso
2013-02-19 7:51 ` [PATCH 7/7] netfilter: nf_ct_helper: Fix " Joe Perches
2013-02-19 20:17 ` Pablo Neira Ayuso
2013-02-19 5:44 ` [PATCH 0/7] netfilter updates for net-next David Miller
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=1361237017.2046.9.camel@joe-AO722 \
--to=joe@perches.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
/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).