From: "Tal Dayan" <tal@zapta.com>
To: <linux-kernel@vger.kernel.org>
Subject: CPU usage 'leak' with port redirection
Date: Sun, 30 Sep 2001 20:45:21 -0700 [thread overview]
Message-ID: <LOBBJKOICNAKIBJGONPJOEOLAAAB.tal@zapta.com> (raw)
In-Reply-To: <200109282157.OAA07885@gormenghast.vista>
Hello,
I am new to this list.
We are straggling for several months with the bug documented at
http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=46665 and we positively
confirmed that the problem disappears when we remove the redirection from
the
ipchains script.
Is there any formal procedure or a place to submit kernel related bugs ? I
could not
find anything about it at www.kernel.org.
Also, is the redirection code of the kernel shared between ipchains and
iptables or is it possible that the bug will not manifest itself if
we switch to iptables.
(we are using Linux version 2.4.2-2, Red Hat Linux 7.1 2.96-79)
Any help will be greatly appreciated,
Tal
prev parent reply other threads:[~2001-10-01 3:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-28 21:57 Patches to enable ia32 NUMA system (32 proc) Martin J. Bligh
2001-09-28 22:14 ` Linus Torvalds
2001-09-28 23:14 ` Martin J. Bligh
2001-10-01 3:45 ` Tal Dayan [this message]
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=LOBBJKOICNAKIBJGONPJOEOLAAAB.tal@zapta.com \
--to=tal@zapta.com \
--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
all inboxes | Powered by JetHome®