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: <20231130152041.13513-1-pctammela@mojatatu.com> Date: Thu, 30 Nov 2023 12:20:37 -0300 From: Pedro Tammela <pctammela@...atatu.com> To: netdev@...r.kernel.org Cc: davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org, pabeni@...hat.com, jhs@...atatu.com, xiyou.wangcong@...il.com, jiri@...nulli.us, mleitner@...hat.com, Pedro Tammela <pctammela@...atatu.com> Subject: [PATCH net-next 0/4] net/sched: act_api: contiguous action arrays When dealing with action arrays in act_api it's natural to ask if they are always contiguous (no NULL pointers in between). Yes, they are in all cases so far, so make use of the already present tcf_act_for_each_action macro to explicitly document this assumption. There was an instance where it was not, but it was refactorable (patch 2) to make the array contiguous. Pedro Tammela (4): net/sched: act_api: use tcf_act_for_each_action net/sched: act_api: avoid non-contiguous action array net/sched: act_api: stop loop over ops array on NULL in tcf_action_init net/sched: act_api: use tcf_act_for_each_action in tcf_idr_insert_many net/sched/act_api.c | 57 ++++++++++++++++++++++++--------------------- 1 file changed, 30 insertions(+), 27 deletions(-) -- 2.40.1
Powered by blists - more mailing lists