From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Kevin Cernekee <cernekee@chromium.org>
Cc: dianders@chromium.org, davem@davemloft.net,
netfilter-devel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2 1/2] netfilter: ctnetlink: Fix regression in CTA_STATUS processing
Date: Mon, 6 Feb 2017 12:44:32 +0100 [thread overview]
Message-ID: <20170206114432.GA15498@salvia> (raw)
In-Reply-To: <20170126224944.29047-1-cernekee@chromium.org>
On Thu, Jan 26, 2017 at 02:49:43PM -0800, Kevin Cernekee wrote:
> The libnetfilter_conntrack userland library always sets IPS_CONFIRMED
> when building a CTA_STATUS attribute. If this toggles the bit from
> 0->1, the parser will return an error. On Linux 4.4+ this will cause any
> NFQA_EXP attribute in the packet to be ignored. This breaks conntrackd's
> userland helpers because they operate on unconfirmed connections.
>
> Instead of returning -EBUSY if the user program asks to modify an
> unchangeable bit, simply ignore the change.
>
> Also, fix the logic so that user programs are allowed to clear
> the bits that they are allowed to change.
Applied, thanks Kevin.
I have manually fixed here this compilation warning, btw:
net/netfilter/nf_conntrack_netlink.c:1449:1: warning:
‘ctnetlink_update_status’ defined but not used [-Wunused-function] ctnetlink_update_status(struct nf_conn *ct, const struct nlattr * const cda[])
^
prev parent reply other threads:[~2017-02-06 11:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-26 22:49 [PATCH V2 1/2] netfilter: ctnetlink: Fix regression in CTA_STATUS processing Kevin Cernekee
2017-01-26 22:49 ` [PATCH V2 2/2] netfilter: ctnetlink: Fix regression in CTA_HELP processing Kevin Cernekee
2017-02-06 11:44 ` Pablo Neira Ayuso
2017-02-06 11: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=20170206114432.GA15498@salvia \
--to=pablo@netfilter.org \
--cc=cernekee@chromium.org \
--cc=davem@davemloft.net \
--cc=dianders@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--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).