All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kasprzak <kas@fi.muni.cz>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Patrick McHardy <kaber@trash.net>, netfilter-devel@vger.kernel.org
Subject: Re: iptables: Resource temporarily unavailable.
Date: Thu, 11 Nov 2010 19:03:05 +0100	[thread overview]
Message-ID: <20101111180305.GD20871@fi.muni.cz> (raw)
In-Reply-To: <1289498295.17691.1589.camel@edumazet-laptop>

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?

	Thanks,

-Yenya

-- 
| Jan "Yenya" Kasprzak  <kas at {fi.muni.cz - work | yenya.net - private}> |
| GPG: ID 1024/D3498839      Fingerprint 0D99A7FB206605D7 8B35FCDE05B18A5E |
| http://www.fi.muni.cz/~kas/    Journal: http://www.fi.muni.cz/~kas/blog/ |
Please don't top post and in particular don't attach entire digests to your
mail or we'll all soon be using bittorrent to read the list.     --Alan Cox

  reply	other threads:[~2010-11-11 18:03 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 [this message]
2010-11-11 18:10           ` Michał Mirosław
2010-11-11 18:20           ` Eric Dumazet
2010-11-12  7:38             ` Patrick McHardy

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=20101111180305.GD20871@fi.muni.cz \
    --to=kas@fi.muni.cz \
    --cc=eric.dumazet@gmail.com \
    --cc=kaber@trash.net \
    --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.