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: Wed, 09 Mar 2016 16:10:38 -0500 (EST) From: David Miller <davem@...emloft.net> To: gorcunov@...il.com Cc: alexei.starovoitov@...il.com, eric.dumazet@...il.com, netdev@...r.kernel.org, solar@...nwall.com, vvs@...tuozzo.com, avagin@...tuozzo.com, xemul@...tuozzo.com, vdavydov@...tuozzo.com, khorenko@...tuozzo.com, pablo@...filter.org, netfilter-devel@...r.kernel.org Subject: Re: [RFC] net: ipv4 -- Introduce ifa limit per net From: Cyrill Gorcunov <gorcunov@...il.com> Date: Wed, 9 Mar 2016 23:57:47 +0300 > Aha! So in your patch __inet_del_ifa bypass first blocking_notifier_call_chain > > __inet_del_ifa > ... > if (in_dev->dead) > goto no_promotions; > > // First call to NETDEV_DOWN > ... > no_promotions: > rtmsg_ifa(RTM_DELADDR, ifa1, nlh, portid); > blocking_notifier_call_chain(&inetaddr_chain, NETDEV_DOWN, ifa1); > > and here we call for NETDEV_DOWN, which then hits masq_device_event > and go further to conntrack code. Yes that's where the notifier comes from, which happens with or without my patch.
Powered by blists - more mailing lists