From: Alessandro Vesely <vesely@tana.it>
To: netfilter@vger.kernel.org
Subject: Cannot destroy queue, nfnl_talk never returns
Date: Sat, 12 Jun 2010 13:20:16 +0200 [thread overview]
Message-ID: <4C136D70.3050902@tana.it> (raw)
Hi,
it has happened again (previous time was 5 May 2010).
This time I used gdb rather than strace, but still don't know what's wrong:
Calling recv on the nfq_fd had returned -512. (why?)
At that point my daemon calls nfq_destroy_queue(), which does not return:
(gdb) bt
#0 0x00007ff3b6e50450 in recvfrom () from /lib/libc.so.6
#1 0x00007ff3b696105c in nfnl_talk () from /usr/lib/libnfnetlink.so.0
#2 0x00007ff3b79a429f in __build_send_cfg_msg (h=0x6073a0, command=2 '\002', queuenum=<value optimized out>, pf=0)
at libnetfilter_queue.c:112
#3 0x00007ff3b79a430d in nfq_destroy_queue (qh=0x607410) at libnetfilter_queue.c:258
#4 0x00000000004021f7 in daemon_loop (h=0x6073a0, db=0x606570) at ibd-judge.c:477
#5 0x0000000000402a75 in main (argc=<value optimized out>, argv=<value optimized out>) at ibd-judge.c:739
Any idea?
TIA
next reply other threads:[~2010-06-12 11:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-12 11:20 Alessandro Vesely [this message]
2010-06-13 23:21 ` Cannot destroy queue, nfnl_talk never returns Pablo Neira Ayuso
2010-06-14 18:15 ` Alessandro Vesely
2010-07-03 11:15 ` recv fails with ENOBUFS (was: Cannot destroy queue, Alessandro Vesely
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=4C136D70.3050902@tana.it \
--to=vesely@tana.it \
--cc=netfilter@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.