From: Patrick McHardy <kaber@trash.net>
To: Jesper Dangaard Brouer <hawk@comx.dk>
Cc: Jesper Dangaard Brouer <hawk@diku.dk>,
netfilter-devel@lists.netfilter.org
Subject: Re: Concurrency issues with the iptables userspace program andexitcodes
Date: Mon, 19 Jun 2006 18:29:14 +0200 [thread overview]
Message-ID: <4496D0DA.6030300@trash.net> (raw)
In-Reply-To: <1150296040.26187.114.camel@localhost.localdomain>
Jesper Dangaard Brouer wrote:
> Hmmm... I though I did include it inline below my signature... well lets
> try again...This time I also attach it as a file attachment.
Applied, thanks. I got a reject on the libiptc part, so I just left
it out.
> diff --exclude '*.d' --exclude-from /var/kernel/exclude_these -urpN iptables-1.3.4-pom-l7/libiptc/libiptc.c iptables-1.3.4-pom-l7-blocking/libiptc/libiptc.c
> --- iptables-1.3.4-pom-l7/libiptc/libiptc.c 2005-10-31 20:03:49.000000000 +0100
> +++ iptables-1.3.4-pom-l7-blocking/libiptc/libiptc.c 2006-06-07 10:25:02.000000000 +0200
> @@ -2104,6 +2104,7 @@ TC_COMMIT(TC_HANDLE_T *handle)
> free(repl->counters);
> free(repl);
> free(newcounters);
> + // The "EAGAIN: Resource temporarily unavailable" occurs here.
> return 0;
> }
>
prev parent reply other threads:[~2006-06-19 16:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-01 9:15 Concurrency issues with the iptables userspace program andexitcodes Jesper Dangaard Brouer
2006-06-01 16:13 ` Patrick McHardy
2006-06-01 20:16 ` Jesper Dangaard Brouer
2006-06-01 20:45 ` Patrick McHardy
2006-06-08 12:52 ` Jesper Dangaard Brouer
2006-06-14 14:05 ` Patrick McHardy
2006-06-14 14:40 ` Jesper Dangaard Brouer
2006-06-19 16:29 ` 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=4496D0DA.6030300@trash.net \
--to=kaber@trash.net \
--cc=hawk@comx.dk \
--cc=hawk@diku.dk \
--cc=netfilter-devel@lists.netfilter.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.