James Morris wrote: > I've been looking through the kernel for new subsytems which might need > LSM hooks, and we've got a proliferation of Netlink abstractions: generic > Netlink, nfnetlink, connector and kobject_uevent. > > I think we should look at consolidating some of these schemes, and if > possible, into a unififed Netlink API. > > As a first step, what would it take to adapt the single user of > connector (the w1 driver) to use generic Netlink? > > I suspect that some of the nfnetlink infrastructure can be used more > generically, and that a simple API for the common case of kernel->user > event notifications could be also be provided. > > Thoughts?
No great thoughts at this point, but I agree 100%. In my opinion netlink subsystems should be usable in a uniform way (at least netlink specific parts like dump/query/set, ACKs, attribute encoding and similar low-level stuff) without implementation specific details. I guess from a SELinux point of view having a single spot to place hooks with well defined semantics is what counts, but it comes down to the same, there is too much diversion among netlink users. I'll look into the nfnetlink bits for a start, but I fear because of use of network byteorder in lots of places it will not be able to fully convert to generic netlink. - 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
