Hi, On Mon, Jul 02, 2018 at 03:28:04PM +0200, Clément Péron wrote: > Could you review it please ? > sorry... I was thinking a lot what I can contribute to this patch, I want to make it short. I see your use case and your use case has of course a valid point. What I can say about the code? This socket layer was contributed a lot in a time where the subsystem was unmaintained. Stefan has some experience with this socket layer by doing some examples [0]. In my opinion I am confused that a lot of netlink handling is needed to do "something" with this socket layer. I already thought that we need some af802154ng for next generation. Known bug is also RAW sockets on af802154 are totally messed up... but we don't need them, this can be done by AF_PACKET (just need to think about similar handling there). --- Now to your patch, you use skb->cb there. The tc ingress part can _maybe_? use this control block information. I think this issue is out of scope because we have also other parts in the code how we pass data between driver and packet layer with skb->cb -> we simply do it wrong. I have no problems to have this patch inside but for future we should tackle a af802154ng with a better UAPI handling. If we fix skb->cb we just need to think about how to pass such data up to socket layer. - Alex [0] https://github.com/linux-wpan/wpan-tools/tree/master/examples -- To unsubscribe from this list: send the line "unsubscribe linux-wpan" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
