From: Herbert Xu <herbert@gondor.apana.org.au>
To: cfriesen@nortel.com (Christopher Friesen)
Subject: Re: netlink nlmsg_pid supposed to be pid or tid?
Cc: kuznet@ms2.inr.ac.ru, herbert@gondor.apana.org.au, netdev@vger.kernel.org,
       linux-kernel@vger.kernel.org, davem@davemloft.net
Organization: Core
In-Reply-To: <4382406D.1040508@nortel.com>
User-Agent: tin/1.7.4-20040225 ("Benbecula") (UNIX) (Linux/2.4.27-hx-1-686-smp (i686))
Message-Id: <E1EeJwF-0006wc-00@gondolin.me.apana.org.au>
Date: Tue, 22 Nov 2005 09:15:03 +1100
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1027
Lines: 24

Christopher Friesen <cfriesen@nortel.com> wrote:
> 
> When an NPTL child thread uses getpid() to specify the pid, it never 
> receives a response to this request.  Running the same code on the 
> parent works, and running the same code under Linuxthreads works.

As I said before, you should not rely on getpid() to work.  Any other
process in the system can bind to your pid which makes it unavailable
to your process.  In which case the kernel will pick an arbitrary
negative pid as your address.

You should always use getsockaddr(2) to get your local address.

Cheers,
-- 
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/