* Herbert Xu <[EMAIL PROTECTED]> 2006-08-16 21:39 > For a broadcast notification, the nlmsg_pid field is meaningless > because the nlmsg_seq field is also meaningless. I'm not denying > that it wouldn't be useful to have the originator's socket address > in there. What I'm saying is that it's the wrong place to put > that information.
It might not be the best place to put it considering the original intend of nlmsg_pid as you explained correctly. However, as you state yourself, the nlmsg_pid field is meaningless/unused for notifications so extending the definition of nlmsg_pid to have a special meaning for broadcasts doesn't harm anyone. When setting nlmsg_seq to the seq of the request it becomes a meaning together with nlmsg_pid as applications can then easly assign notifications to their own sent requests. Secondly we already have applications depending on this whereas the eventual breaking of aplications depending on nlmsg_pid == 0 is uncertain. - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
