Hello there, > For the longest time there was no docs or best practices for netlink. > We have the documentation and more infrastructure in place now. > I hope if you wrote the code today the distinction would have been > clearer. > > If we start adding APIs for various one-(two?)-offs from the past > we'll never dig ourselves out of the "no idea what's the normal use > of these APIs" hole.. This is true. Actually, those check missing codes are mostly old codes and modern netlink consumers will choose the general netlink interface which can automatically get attributes description from YAML and never need to do things like *manual parsing* anymore. However, according to my practice in auditing the code, I found there are some general netlink interface users confront other issues like choosing GENL_DONT_VALIDATE_STRICT without thinking or forgetting add a new nla_policy when introducing new attributes. To this end, I'm currently writing a simple documentation about Netlink interface best practices for the kernel developer (the newly coming docs are mostly about the user API part). I guess I will put this doc in Documentation/staging :) and I will finish the draft ASAP. Thanks Lin
