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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Wed, 26 Oct 2022 21:40:11 +0200 From: Michael Lilja <michael.lilja@...il.com> To: Pablo Neira Ayuso <pablo@...filter.org> Cc: "David S. Miller" <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>, Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>, Jonathan Corbet <corbet@....net>, Jozsef Kadlecsik <kadlec@...filter.org>, Florian Westphal <fw@...len.de>, netdev@...r.kernel.org, linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org, netfilter-devel@...r.kernel.org, coreteam@...filter.org Subject: Re: [PATCH] Periodically flow expire from flow offload tables Hi, I just quickly tried following the flow_offload_teardown() path instead of clearing IPS_OFFLOAD in flow_offload_del() and it does have some side effects. The flow is added again before the HW has actually reported it to be NF_FLOW_HW_DEAD. The sequence with my patch is: : Retire -> Remove from hw tables -> Remove from sw tables -> kfree(flow) -> flow_offload_add() But if flow_offload_teardown() is called on expire I see: : Retire -> Remove from hw tables -> flow_offload_add() -> Remove from sw tables -> kfree(flow) I need to investigate why this happens, maybe the IPS_OFFLOAD flag is cleared too early and should not be cleared until the flow is actually removed, like I do? Maybe the issue is not seen before because on timeout or flow_is_dying() no packet arrive to create the flow again prematurely? Thanks, Michael
Powered by blists - more mailing lists