From: Peter Enderborg <pme@ufh.se>
To: linux kermel <linux-kernel@vger.kernel.org>
Subject: Strange kernel logging
Date: Sun, 21 Apr 2002 10:51:33 +0200 [thread overview]
Message-ID: <3CC27D95.6A9F252F@ufh.se> (raw)
I was playing with nmap and tryed to do portscan on my 2.4.18 kernel
with iptables.
I use port -sS -p 1 to search all ports. And I have iptables to do
logging on all
rejected messags. The scan mod was "norlmal" and that sends messags in
bursts.
And when this burts was recived the machine was very slo and had
keyboard problems.
It was very low latency for the keyevents. It was funny to see what
happend when
key relase event was delayed. A lot of same chars... This is on a dual
PII and
I guess that it is some race condition with in the logging in iptables.
Is this
a known problem? Any one that have solution?
reply other threads:[~2002-04-21 8:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3CC27D95.6A9F252F@ufh.se \
--to=pme@ufh.se \
--cc=linux-kernel@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