From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Arturo Borrero Gonzalez <arturo.borrero.glez@gmail.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [libnftnl PATCH 1/2] src: add flag to add event wrapping in output functions
Date: Tue, 15 Apr 2014 15:44:31 +0200 [thread overview]
Message-ID: <20140415134431.GA8927@localhost> (raw)
In-Reply-To: <20140415125030.2590.5501.stgit@nfdev.cica.es>
On Tue, Apr 15, 2014 at 02:50:30PM +0200, Arturo Borrero Gonzalez wrote:
> diff --git a/src/chain.c b/src/chain.c
> index 472203e..87558a1 100644
> --- a/src/chain.c
> +++ b/src/chain.c
> @@ -924,17 +924,44 @@ static int nft_chain_snprintf_default(char *buf, size_t size,
> int nft_chain_snprintf(char *buf, size_t size, struct nft_chain *c,
> uint32_t type, uint32_t flags)
> {
> + int ret, len = size, offset = 0;
> +
> + if (flags & (1 << NFT_OUTPUT_FLAG_EVENTNEW)) {
> + ret = snprintf(buf+offset, len, "%s",
> + nft_event_opentag(NFT_OUTPUT_FLAG_EVENTNEW,
> + type));
> + SNPRINTF_BUFFER_SIZE(ret, size, len, offset);
> + } else if (flags & (1 << NFT_OUTPUT_FLAG_EVENTDEL)) {
> + ret = snprintf(buf+offset, len, "%s",
> + nft_event_opentag(NFT_OUTPUT_FLAG_EVENTDEL,
> + type));
> + SNPRINTF_BUFFER_SIZE(ret, size, len, offset);
> + }
> +
[...]
> + if (flags & (1 << NFT_OUTPUT_FLAG_EVENTNEW)) {
> + ret = snprintf(buf+offset, len, "%s",
> + nft_event_opentag(NFT_OUTPUT_FLAG_EVENTNEW,
> + type));
> + SNPRINTF_BUFFER_SIZE(ret, size, len, offset);
> + noevent_flags &= ~(1 << NFT_OUTPUT_FLAG_EVENTNEW);
> + } else if (flags & (1 << NFT_OUTPUT_FLAG_EVENTDEL)) {
> + ret = snprintf(buf+offset, len, "%s",
> + nft_event_opentag(NFT_OUTPUT_FLAG_EVENTDEL,
> + type));
> + SNPRINTF_BUFFER_SIZE(ret, size, len, offset);
> + noevent_flags &= ~(1 << NFT_OUTPUT_FLAG_EVENTDEL);
> + }
This code looks very similar, you can encapsulate it in one function
to add the heading and the trailer.
Regarding the noevent_flags thing, which is the only different, you can do:
unsigned int inner_flags &= ~NFT_OF_EVENT_ANY;
And use inner_flags to when you have nested calls (ie. like in ruleset.c).
The NFT_OF_EVENT_ANY mask should be something like:
enum ... {
NFT_OF_EVENT_ANY = (NFT_OF_EVENT_NEW | NFT_OF_EVENT_DEL)
};
Thanks.
prev parent reply other threads:[~2014-04-15 13:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-15 12:50 [libnftnl PATCH 1/2] src: add flag to add event wrapping in output functions Arturo Borrero Gonzalez
2014-04-15 12:50 ` [libnftnl PATCH 2/2] examples: nft-events: use new events wrappers Arturo Borrero Gonzalez
2014-04-15 13:36 ` [libnftnl PATCH 1/2] src: add flag to add event wrapping in output functions Pablo Neira Ayuso
2014-04-15 13:44 ` Pablo Neira Ayuso [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=20140415134431.GA8927@localhost \
--to=pablo@netfilter.org \
--cc=arturo.borrero.glez@gmail.com \
--cc=netfilter-devel@vger.kernel.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).