From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Florian Westphal <fwestphal@astaro.com>
Cc: netfilter-devel@vger.kernel.org, davem@davemloft.net
Subject: Re: [PATCH] netfilter: ctnetlink: fix loop in ctnetlink_get_conntrack()
Date: Thu, 13 Jan 2011 17:00:20 +0100 [thread overview]
Message-ID: <4D2F2194.4000601@netfilter.org> (raw)
In-Reply-To: <1294924795-20816-1-git-send-email-fwestphal@astaro.com>
On 13/01/11 14:19, Florian Westphal wrote:
> From: Pablo Neira Ayuso <pablo@netfilter.org>
>
> This patch fixes a loop in ctnetlink_get_conntrack() that can be
> triggered if you use the same socket to receive events and to
> perform a GET operation. Under heavy load, netlink_unicast()
> may return -EAGAIN, this error code is reserved in nfnetlink for
> the module load-on-demand. Instead, we return -ENOBUFS which is
> the appropriate error code that has to be propagated to
> user-space.
Indeed, it's in Patrick's tree but it didn't get the patch to reach the
kernel. I'll pass it to davem.
prev parent reply other threads:[~2011-01-13 16:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-13 13:19 [PATCH] netfilter: ctnetlink: fix loop in ctnetlink_get_conntrack() Florian Westphal
2011-01-13 16:00 ` 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=4D2F2194.4000601@netfilter.org \
--to=pablo@netfilter.org \
--cc=davem@davemloft.net \
--cc=fwestphal@astaro.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).