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
| ||
|
Date: Thu, 18 Aug 2022 19:53:01 -0700 From: Jakub Kicinski <kuba@...nel.org> To: Jiri Pirko <jiri@...nulli.us> Cc: netdev@...r.kernel.org, davem@...emloft.net, idosch@...dia.com, pabeni@...hat.com, edumazet@...gle.com, saeedm@...dia.com, jacob.e.keller@...el.com, vikas.gupta@...adcom.com, gospo@...adcom.com Subject: Re: [patch net-next 4/4] net: devlink: expose default flash update target On Thu, 18 Aug 2022 15:00:42 +0200 Jiri Pirko wrote: > Allow driver to mark certain version obtained by info_get() op as > "flash update default". Expose this information to user which allows him > to understand what version is going to be affected if he does flash > update without specifying the component. Implement this in netdevsim. My intuition would be that if you specify no component you're flashing the entire device. Is that insufficient? Can you explain the use case? Also Documentation/ needs to be updated.
Powered by blists - more mailing lists