All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anton <anton.vazir@gmail.com>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel <netfilter-devel@vger.kernel.org>
Subject: Re: (nfnl_talk: recvmsg over-run) and (nf_queue: full at 1024 	entries, dropping packets(s). Dropped: 582) - bug or just some defaults 	increase required?
Date: Thu, 12 Feb 2009 15:45:14 +0500	[thread overview]
Message-ID: <200902121545.16590.anton.vazir@gmail.com> (raw)
In-Reply-To: <4992FFD7.9090706@netfilter.org>

Pablo,

Some more info. After applying the patch, If we do try to 
just create 100 QUEUE's by the test code - on the test PC, 
with _no_ transit traffic, routed to QUEUE's - it works 
fine, queues created with no problem. 
But if we do this on the live PC, with trasit traffic routed 
to queues - we came to the problem once in a few queues. 
We localized the place, and the sequence is as follows:
nfnl_query=>nfnl_catch=>nfnl_process

and in the nfnl_process

if (nlh->nlmsg_seq && nlh->nlmsg_seq != h->seq) {
                errno = EILSEQ;
                return -1;
}

and varibales are
nlh->msg_seq=1234422225, h->seq=1234422229.

EILSEQ=84
strerr(84) returns "Invalid or incomplete multibyte or wide 
character"

Any clue on this?

Regards,
Anton.

On Wednesday 11 February 2009 21:41, Pablo Neira Ayuso 
wrote:
> Anton VG wrote:
> > Pablo,
> >
> > On 64bit system, after applying the patch,
> > nfq_create_queue() started to oftenly return NULL, and
> > calling
> > strerror(errno) - I've got a error "Invalid or
> > incomplete multibyte or wide character".
> >
> > On 32bit it works. This have been tested with only 2x
> > simultaneous queues Any thoughts?
>
> Let me check this. Do you think that I can reproduce it
> with the test file in libnetfilter_queue? If you can pass
> something similar to your code to reproduce the problem,
> it would be great. Thanks.

  reply	other threads:[~2009-02-12 10:45 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-06 18:14 (nfnl_talk: recvmsg over-run) and (nf_queue: full at 1024 entries, dropping packets(s). Dropped: 582) - bug or just some defaults increase required? Anton VG
2009-02-08  1:34 ` Pablo Neira Ayuso
2009-02-09 10:56   ` Anton
2009-02-09 11:20     ` Pablo Neira Ayuso
2009-02-11  8:48       ` Anton
     [not found]       ` <49928B62.1090600@netfilter.org>
2009-02-11 12:26         ` Anton VG
2009-02-11 16:41           ` Pablo Neira Ayuso
2009-02-12 10:45             ` Anton [this message]
2009-02-12 12:43               ` Pablo Neira Ayuso
2009-02-14  9:03                 ` Anton
2009-02-14 17:13               ` Pablo Neira Ayuso
2009-02-16 13:19                 ` Anton
2009-02-16 13:42                   ` Pablo Neira Ayuso
2009-02-16 14:38                     ` Anton VG
2009-02-16 15:23                       ` Pablo Neira Ayuso
2009-02-16 15:33                         ` Anton VG
2009-02-16 15:41                           ` Anton VG
2009-02-17 16:58                             ` Anton VG
2009-02-17 17:15                               ` Pablo Neira Ayuso
2009-02-17 17:31                                 ` Anton VG
2009-02-18  2:48                                   ` Amos Jeffries
2009-02-17 17:34                                 ` Anton VG
2009-02-17 19:51                                   ` Pablo Neira Ayuso

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=200902121545.16590.anton.vazir@gmail.com \
    --to=anton.vazir@gmail.com \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=pablo@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.