From: Rusty Russell <rusty@rustcorp.com.au>
To: Matt Bernstein <matt@theBachChoir.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.7 crash with ipchains/netfilter as modules
Date: Wed, 25 Jul 2001 20:03:34 +1000 [thread overview]
Message-ID: <m15PLVv-000CDBC@localhost> (raw)
In-Reply-To: Your message of "Wed, 25 Jul 2001 11:04:04 +0100." <Pine.LNX.4.33.0107251054420.1834-100000@nick.dcs.qmw.ac.uk>
In message <Pine.LNX.4.33.0107251054420.1834-100000@nick.dcs.qmw.ac.uk> you wri
te:
> ipchains 37568 0 (unused)
> unix 16992 27 (autoclean)
>
> ..but "ipchains -L" does produce some output (though it takes many
> minutes), and the kernel has logged some DENY packets. Attempting
> "modprobe -r ipchains" gives the following (possibly meaningless) oops.
Known issue (usage count stays at 0, independent of usage).
Try ipchains -L -n to get your output.
I'll look into the removal code (Al found some loading problems before
which I want to fix anyway)...
Thanks,
Rusty.
--
Premature optmztion is rt of all evl. --DK
next prev parent reply other threads:[~2001-07-25 12:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-25 10:04 2.4.7 crash with ipchains/netfilter as modules Matt Bernstein
2001-07-25 10:03 ` Rusty Russell [this message]
2001-07-29 20:57 ` Rusty Russell
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=m15PLVv-000CDBC@localhost \
--to=rusty@rustcorp.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@theBachChoir.org.uk \
/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