All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pablo Neira <pablo@eurodev.net>
To: Henrik Nordstrom <hno@marasystems.com>,
	netfilter-devel@lists.netfilter.org,
	Patrick McHardy <kaber@trash.net>,
	Harald Welte <laforge@netfilter.org>
Subject: Re: [PATCH] peer_pid checking in ip_queue
Date: Wed, 24 Mar 2004 01:42:17 +0100	[thread overview]
Message-ID: <4060D969.9040900@eurodev.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0403240106490.15222-100000@filer.marasystems.com>

Hi,

Henrik Nordstrom wrote:

>What about when the user program closes? How bad it is to have read the 
>pid and then there is no userspace there?
>  
>
As Patrick pointed out before, netlink is not reliable, so it will drop 
the packets sent to an user space which doesn't exist without 
notification. But if the user space program closes properly, peer_pid 
will be reset. Have a look at ipq_rcv_nl_event and netlink_release. 
AFAIK, if the user space program hangs or dies, kernel will release the 
socket later, so for quite some time netlink will drop packets. Am I right?

regards,
Pablo

  reply	other threads:[~2004-03-24  0:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-23 11:09 [PATCH] peer_pid checking in ip_queue Pablo Neira
2004-03-23 17:25 ` Patrick McHardy
2004-03-23 18:10   ` Pablo Neira
2004-03-23 22:44     ` Patrick McHardy
2004-03-24  0:07       ` Henrik Nordstrom
2004-03-24  0:42         ` Pablo Neira [this message]
2004-03-24  2:11           ` Patrick McHardy
2004-03-24  0:47         ` Patrick McHardy
2004-03-27 21:20       ` Harald Welte
2004-03-27 23:50         ` Patrick McHardy
2004-03-27 21:17 ` Harald Welte

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=4060D969.9040900@eurodev.net \
    --to=pablo@eurodev.net \
    --cc=hno@marasystems.com \
    --cc=kaber@trash.net \
    --cc=laforge@netfilter.org \
    --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.