Linux Netfilter development
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: "Dâniel Fraga" <fragabr@gmail.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: Every other char with LOG netfilter output (bug?)
Date: Tue, 28 Oct 2008 18:40:17 +0100	[thread overview]
Message-ID: <49074E81.6010207@trash.net> (raw)
In-Reply-To: <rlujt5-k63.ln1@tux.abusar.org.br>

Dâniel Fraga wrote:
> 	Since Linux kernel 2.6.25, I get stalled connections and when it happens, I have this on the log:
> 
> Oct 28 13:39:22 tux vmunix: 1:3e:79:01:fe:b2:80 R=9.6.. S=9.6.. E=9
> O=x0PE=x0TL6 D410POOUPST10 P=41 E=7
> 
> 	It seems that are missing chars here.
> 
> 	A bug?

Seems likely. Is that an SMP machine? Its possible that the ringbuffer
simply overflows before the logging daemon gets a chance to capture it,
but that should only cause truncated lines.

What do your logging rules that might be responsible for this look like?

> 	Ps: in fact this issue seems to be much more complex than this. There's a huge thread we 
> talked about those stalled connections, but we are unable to discover what causes this, so I opened 
> this bug report:
> 
> http://bugzilla.kernel.org/show_bug.cgi?id=11588
> 
> 	At least if netfilter developers could figure it out why the above log line happens, maybe we 
> could trace this bug and solve it.

I can't see anything in that report that would ring a bell.
Are you using any of the more unusual networking features,
like QoS, policy routing etc?

--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2008-10-28 17:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-28 17:09 Every other char with LOG netfilter output (bug?) Dâniel Fraga
2008-10-28 17:40 ` Patrick McHardy [this message]
2008-10-28 17:57   ` Dâniel Fraga
2008-10-28 18:13     ` Patrick McHardy
2008-10-28 18:50       ` Jan Engelhardt
2008-10-28 18:53         ` Patrick McHardy
2008-10-28 19:16       ` Dâniel Fraga
2008-10-30  5:50       ` Dâniel Fraga
2008-10-30  7:15         ` Patrick McHardy
2008-10-30 15:02           ` Pablo Neira Ayuso
2008-10-30 23:23           ` Dâniel Fraga
2008-10-31  2:01           ` Dâniel Fraga
2008-11-03 12:42             ` Patrick McHardy
2008-11-03 15:41               ` Dâniel Fraga

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=49074E81.6010207@trash.net \
    --to=kaber@trash.net \
    --cc=fragabr@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox