From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: "Dâniel Fraga" <fragabr@gmail.com>, netfilter-devel@vger.kernel.org
Subject: Re: Every other char with LOG netfilter output (bug?)
Date: Tue, 28 Oct 2008 19:53:37 +0100 [thread overview]
Message-ID: <49075FB1.7050803@trash.net> (raw)
In-Reply-To: <alpine.LNX.1.10.0810281447540.9876@fbirervta.pbzchgretzou.qr>
Jan Engelhardt wrote:
> On Tuesday 2008-10-28 14:13, Patrick McHardy wrote:
>>> The interesting is that this behaviour started at 2.6.25 kernel
>>> version, but
>>> I couldn't find anything that was changed between .24 and .25 to cause this.
>>> Very strange.
>> I have no idea why the log output is corrupted like this, but
>> some things you could try:
>>
>> - use serial console, which should at least avoid any corruption
>> triggered by ringbuffer overflows. It many packets are logged
>> it will slow down your system considerably though.
>
> JFYI, if it was a ring issue, the start of the string would be
> overwritten, and not just random chars.
I know, but judging by the few things that look like valid
LOG fragments, there seems to be more corruption than just
the ring buffer going on, so it might be worth a try.
I'd try nfnetlink_log first though.
next prev parent reply other threads:[~2008-10-28 18:53 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
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 [this message]
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=49075FB1.7050803@trash.net \
--to=kaber@trash.net \
--cc=fragabr@gmail.com \
--cc=jengelh@medozas.de \
--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 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.