From: "Christopher Friesen" <cfriesen@nortel.com>
To: Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
davem@davemloft.net
Subject: Re: netlink nlmsg_pid supposed to be pid or tid?
Date: Mon, 21 Nov 2005 15:47:25 -0600 [thread overview]
Message-ID: <4382406D.1040508@nortel.com> (raw)
In-Reply-To: <20051121213549.GA28187@ms2.inr.ac.ru>
Alexey Kuznetsov wrote:
> Hello!
>
>
>>I tend to agree with you here that tgid makes more sense.
>
>
> I agree, apparently netlink_autobind was missed when sed'ing pid->tgid.
> Of course, it does not matter, but tgid is nicer choice from user's viewpoint.
I'm glad you agree, but I'm not sure what you mean by "it does not matter".
TIPC wants the user to fill in the pid to use in the nlmsghdr portion of
a particular message.
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.
Using gettid() works, but it also means that only the thread that issued
the request can read the reply.
Chris
next prev parent reply other threads:[~2005-11-21 21:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-21 19:32 netlink nlmsg_pid supposed to be pid or tid? Christopher Friesen
2005-11-21 19:46 ` Christopher Friesen
2005-11-21 20:51 ` Herbert Xu
2005-11-21 21:35 ` Alexey Kuznetsov
2005-11-21 21:47 ` Christopher Friesen [this message]
2005-11-21 22:15 ` Herbert Xu
2005-11-21 22:51 ` Christopher Friesen
2005-11-22 0:09 ` Herbert Xu
2005-11-21 22:49 ` Alexey Kuznetsov
2005-11-21 23:34 ` Herbert Xu
2005-11-21 22:16 ` [NETLINK]: Use tgid instead of pid for nlmsg_pid Herbert Xu
2005-11-22 22:43 ` David S. Miller
2005-11-23 0:03 ` Herbert Xu
2005-11-23 6:18 ` David S. Miller
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=4382406D.1040508@nortel.com \
--to=cfriesen@nortel.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).