[systemd-devel] [udev] Wrong PID used in netlink socket

[Jan Engelhardt]

On Thursday 2013-10-10 15:36, Kay Sievers wrote:
>
>Note, that the netlink *address* just happens to be the PID in the
>usual case, but it's not necessarily the PID. For netlink t's just a
>number, an address not a PID. The second netlink socket a process
>opens gets a negative address instead of anything related to the PID
>of the caller.

Is there a particular reason we do use the process ID (process group
ID) instead of the thread ID (process ID) when autoselecting the
netlink socket address?