From: Harald Welte <laforge@netfilter.org>
To: Sumit Pandya <sumit@elitecore.com>
Cc: Netfilter Development Mailinglist <netfilter-devel@lists.netfilter.org>
Subject: Re: Re : Re: Logging conntrack with ip_conntrack_destroyed
Date: Tue, 17 Jun 2003 18:22:12 +0200 [thread overview]
Message-ID: <20030617162212.GK936@naboo> (raw)
In-Reply-To: <941489777.1055339533302.JavaMail.root@mailhost.elitecore.com>
[-- Attachment #1: Type: text/plain, Size: 1236 bytes --]
On Wed, Jun 11, 2003 at 07:22:13PM +0530, Sumit Pandya wrote:
> Harald,
> Here is my code. I avoided sending code in previous mail is just in
> the good sense of mail size.
Well, as long as it is < 40k, it's fine.
regarding to your bug/oops: Are you aware that you are trying to invoke
the filesystem layer from within a softirq? I don't think that it's
safe to use filesystem operations outside system call or kernel thread
context.
> Also this list has got many request of per connection accounting
> support. Are you interested to support such a development? Could
> you take this RFP for the developers concern? Thanks,
I very much prefer a solution in userspace. Something based on
ctnetlink notifiers and a logging daemon in userspace should be fine.
> -- Sumit
> P.S. Whenever I'm hopeless, Harald is there ;)
--
- Harald Welte <laforge@netfilter.org> http://www.netfilter.org/
============================================================================
"Fragmentation is like classful addressing -- an interesting early
architectural error that shows how much experimentation was going
on while IP was being designed." -- Paul Vixie
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2003-06-17 16:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-11 13:52 Re : Re: Logging conntrack with ip_conntrack_destroyed Sumit Pandya
2003-06-17 16:22 ` Harald Welte [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=20030617162212.GK936@naboo \
--to=laforge@netfilter.org \
--cc=netfilter-devel@lists.netfilter.org \
--cc=sumit@elitecore.com \
/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.