From: Patrick McHardy <kaber@trash.net>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Jan Kasprzak <kas@fi.muni.cz>, netfilter-devel@vger.kernel.org
Subject: Re: iptables: Resource temporarily unavailable.
Date: Fri, 12 Nov 2010 08:38:06 +0100 [thread overview]
Message-ID: <4CDCEEDE.2090700@trash.net> (raw)
In-Reply-To: <1289499630.17691.1618.camel@edumazet-laptop>
On 11.11.2010 19:20, Eric Dumazet wrote:
> Le jeudi 11 novembre 2010 à 19:03 +0100, Jan Kasprzak a écrit :
>> Eric Dumazet wrote:
>> : > There probably can be some other iptables commands running
>> : > occasionally (automatic blacklisting of some IP addresses, enabling
>> : > traffic to authenticated laptops, etc.), but not in the chains I am
>> : > trying to modify with my firewall initscript. Can this also be a problem?
>> :
>> : Yes it is a problem. iptables manipulates the whole table, not a
>> : subtree.
>>
>> So do you suggest I should implement some kind of user-space
>> locking, or is the current approach of "retry after 1 sec when it fails"
>> OK from the kernel point of view?
>
> You could implement a user-space locking, if the additional delay of the
> "retry after 1 sec" is bothering you ;)
Indeed, that's the best solution. The kernel can't really do anything
about this since incremental ruleset updates are a two-step process.
For dumps we've added retries a while ago, for updates this seems a bit
dangerous.
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2010-11-12 7:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-11 15:00 iptables: Resource temporarily unavailable Jan Kasprzak
2010-11-11 15:35 ` Eric Dumazet
2010-11-11 15:57 ` Patrick McHardy
2010-11-11 17:25 ` Jan Kasprzak
2010-11-11 17:58 ` Eric Dumazet
2010-11-11 18:03 ` Jan Kasprzak
2010-11-11 18:10 ` Michał Mirosław
2010-11-11 18:20 ` Eric Dumazet
2010-11-12 7:38 ` Patrick McHardy [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=4CDCEEDE.2090700@trash.net \
--to=kaber@trash.net \
--cc=eric.dumazet@gmail.com \
--cc=kas@fi.muni.cz \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.