From: Anders Fugmann <afu@fugmann.dhs.org>
To: Kim Jong Tae <dejavu@bora.dacom.co.kr>
Cc: netfilter@lists.netfilter.org
Subject: Re: hook function in NF_IP_LOCAL_IN does not interruptible_sleep_on?
Date: Sun, 15 Sep 2002 16:05:14 +0200 [thread overview]
Message-ID: <3D84939A.9000005@fugmann.dhs.org> (raw)
In-Reply-To: Pine.GSO.3.94K.1020915200933.12847A-100000@bora.dacom.co.kr
Kim Jong Tae wrote:
> Hi all.
>
> I makes hook function, which will communicate with user process
> for each packet's arrival.
> First, hook function sends data to user process and user process sends
> back data. I think that before receiving data from user process, hook
> function must wait. hook func's wait is using interruptible_sleep_on.
> When hook func call interruptible_sleep_on, system hangs!!!
You are calling sleep in_interrupt. This is not allowed.
You forgot to mention how you cummunicate with the userspace process.
Throgh a device-node?
Regards
Anders Fugmann
next prev parent reply other threads:[~2002-09-15 14:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-15 11:13 hook function in NF_IP_LOCAL_IN does not interruptible_sleep_on? Kim Jong Tae
2002-09-15 14:05 ` Anders Fugmann [this message]
2002-09-16 0:58 ` Kim Jong Tae
2002-09-16 3:18 ` James Morris
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=3D84939A.9000005@fugmann.dhs.org \
--to=afu@fugmann.dhs.org \
--cc=dejavu@bora.dacom.co.kr \
--cc=netfilter@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox