Re: netlink nlmsg_pid supposed to be pid or tid?

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.

Alexey
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Follow-Ups:
- [NETLINK]: Use tgid instead of pid for nlmsg_pid
  - From: Herbert Xu <[email protected]>
- Re: netlink nlmsg_pid supposed to be pid or tid?
  - From: "Christopher Friesen" <[email protected]>

References:
- netlink nlmsg_pid supposed to be pid or tid?
  - From: "Christopher Friesen" <[email protected]>
- Re: netlink nlmsg_pid supposed to be pid or tid?
  - From: Herbert Xu <[email protected]>

Prev by Date: Re: question about driver built-in kernel
Next by Date: Re: infinite loop? with mmap, nfs, pwrite, O_DIRECT
Previous by thread: Re: netlink nlmsg_pid supposed to be pid or tid?
Next by thread: Re: netlink nlmsg_pid supposed to be pid or tid?
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]