From: "John A. Sullivan III" <john.sullivan@nexusmgmt.com>
To: netfilter-devel@lists.netfilter.org
Subject: RPC patch creates kernel panic
Date: Thu, 01 Apr 2004 16:03:11 -0500 [thread overview]
Message-ID: <1080853391.6764.15.camel@localhost> (raw)
I would imagine the RPC patch developers are well aware of this but I
have consistently generated kernel panics when using the RPC patch.
This was the case using RedHat with several different kernels > 2.4.18
and patch-o-matic-20030107 (I believe).
I thought I would give patch-o-matic-20031219 a try on SUSE with kernel
2.4.25 from kernel.org patched with StrongSWAN 2.0.1 (FreeS/WAN
successor) to see if it behaved any better. Alas, the same problem.
We have neither the skills nor time to contribute code to this patch but
it is important for us especially for our support of Microsoft shops
with their pervasive use of services spawned off of the port mapper on
135/tcp. If there is anything we can do to help outside of development
such as testing, please let us know - John
--
John A. Sullivan III
Chief Technology Officer
Nexus Management
+1 207-985-7880
john.sullivan@nexusmgmt.com
---
If you are interested in helping to develop a GPL enterprise class
VPN/Firewall/Security device management console, please visit
http://iscs.sourceforge.net
next reply other threads:[~2004-04-01 21:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-01 21:03 John A. Sullivan III [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-04-01 22:34 RPC patch creates kernel panic Daniel Chemko
2004-04-02 0:14 Ian Latter
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=1080853391.6764.15.camel@localhost \
--to=john.sullivan@nexusmgmt.com \
--cc=netfilter-devel@lists.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.