From: Patrick McHardy <kaber@trash.net>
To: "Stanis³aw Pitucha" <viraptor@gmail.com>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: ENOBUFS in nfq under heavy load
Date: Tue, 17 Jul 2007 18:14:22 +0200 [thread overview]
Message-ID: <469CEADE.9080104@trash.net> (raw)
In-Reply-To: <717e7cba0707170913t39a335beod068a9670e55808f@mail.gmail.com>
Stanis³aw Pitucha wrote:
>
> On 7/17/07, Patrick McHardy <kaber@trash.net> wrote:
>> Which kernel version? What exactly do you mean with "it stops"?
>
> 2.6.21.5 generic, stock - no patches
>
> By stops I mean that it hangs on nfq_destroy_queue() if there was
> ENOBUFS before.
Please try to find out what the kernel is doing using sysrq.
> When I connected gdb to it I got the stacktrace from the first post.
> When I break it with ctrl+c, I get:
>
> NFNETLINK answers: No such device
>
> on console and program quits.
>
ENODEV can happen when sending a verdict for or unbinding a non-existant
queue.
next prev parent reply other threads:[~2007-07-17 16:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-17 15:46 ENOBUFS in nfq under heavy load Stanisław Pitucha
2007-07-17 15:56 ` Eric Leblond
2007-07-17 15:56 ` Patrick McHardy
2007-07-17 16:13 ` Stanisław Pitucha
2007-07-17 16:14 ` Patrick McHardy [this message]
2007-07-18 9:47 ` Stanisław Pitucha
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=469CEADE.9080104@trash.net \
--to=kaber@trash.net \
--cc=netfilter-devel@lists.netfilter.org \
--cc=viraptor@gmail.com \
/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.