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: Fri, 2 Aug 2019 17:21:55 -0700 From: Jakub Kicinski <jakub.kicinski@...ronome.com> To: wenxu <wenxu@...oud.cn> Cc: jiri@...nulli.us, pablo@...filter.org, fw@...len.de, netfilter-devel@...r.kernel.org, netdev@...r.kernel.org, John Hurley <john.hurley@...ronome.com> Subject: Re: [PATCH net-next v5 5/6] flow_offload: support get flow_block immediately On Sat, 3 Aug 2019 07:19:31 +0800, wenxu wrote: > > Or: > > > > device unregister: > > - nft block destroy > > - UNBIND cb > > - free driver's block state > > - driver notifier callback > > - free driver's state > > > > No? > > For the second case maybe can't unbind cb? because the nft block is > destroied. There is no way to find the block(chain) in nft. But before the block is destroyed doesn't nft send an UNBIND event to the drivers, always?
Powered by blists - more mailing lists