On Wed, 24 Jan 2024 09:37:31 +0000 Donald Hunter wrote: > > Meaning if the key is not found in current scope we'll silently and > > recursively try outer scopes? Did we already document that? > > I remember we discussed it, can you share a link to that discussion? > > Yes, it silently tries outer scopes. The previous discussion is here: > > https://patchwork.kernel.org/project/netdevbpf/patch/20231130214959.27377-7-donald.hunter@xxxxxxxxx/#25622101 > > This is the doc patch that describes sub-messages: > > https://patchwork.kernel.org/project/netdevbpf/patch/20231215093720.18774-4-donald.hunter@xxxxxxxxx/ > > It doesn't mention searching outer scopes so I can add that to the docs. I'm a tiny bit worried about the mis-ordered case. If the selector attr is after the sub-msg but outer scope has an attr of the same name we'll silently use the wrong one. It shouldn't happen in practice but can we notice the wrong ordering and error out cleanly?
