netdev - Re: RTM_NEWLINK not received by application when connecting multiple devices simultaneously

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 19 Apr 2012 21:54:24 +0200
From:	Kristian Evensen <kristian.evensen@...il.com>
To:	Stephen Hemminger <shemminger@...tta.com>
Cc:	Ben Greear <greearb@...delatech.com>, netdev@...r.kernel.org
Subject: Re: RTM_NEWLINK not received by application when connecting multiple
 devices simultaneously

I spent some more time debugging this now. It turns out that which
interface is seen by my application is not random, it is always the
first one that is connected. This indicates that the bug is that the
netlink message contains information about more than one interface.
However, I am not able to prove this.

When I check for the presence of NLM_F_MULTI, it is always NULL. Also,
the length of the received nlmsg (including payload) always equals the
numbers of bytes I receive from the netlink socket, i.e., all the data
is received.

Based on my understanding of netlink, an nlmsg will only contain one
packet (for example ifinfomsg), unless the NLM_F_MULTI flag is set. Or
am I mistaken?

-Kristian
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html