lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <ZN8tv9bH1Bq8s7SS@nanopsycho> Date: Fri, 18 Aug 2023 10:37:19 +0200 From: Jiri Pirko <jiri@...nulli.us> To: Jakub Kicinski <kuba@...nel.org> Cc: netdev@...r.kernel.org Subject: Re: ynl - mutiple policies for one nested attr used in multiple cmds Fri, Aug 04, 2023 at 09:58:16PM CEST, kuba@...nel.org wrote: >On Fri, 4 Aug 2023 19:29:31 +0200 Jiri Pirko wrote: >> I need to have one nested attribute but according to what cmd it is used >> with, there will be different nested policy. >> >> If I'm looking at the codes correctly, that is not currenly supported, >> correct? >> >> If not, why idea how to format this in yaml file? > >I'm not sure if you'll like it but my first choice would be to skip >the selector attribute. Put the attributes directly into the message. >There is no functional purpose the wrapping serves, right? I have another variation of a similar problem. There might be a different policy for nested attribute for get and set. Example nest: DEVLINK_ATTR_PORT_FUNCTION Any suggestion how to resolve this? Thanks!
Powered by blists - more mailing lists