All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Westphal <fw@strlen.de>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: Florian Westphal <fw@strlen.de>, netfilter-devel@vger.kernel.org
Subject: Re: [PATCH nf] netfilter: conntrack: resched in nf_ct_iterate_cleanup
Date: Fri, 11 Dec 2015 18:21:23 +0100	[thread overview]
Message-ID: <20151211172123.GA12854@breakpoint.cc> (raw)
In-Reply-To: <20151211171659.GA1135@salvia>

Pablo Neira Ayuso <pablo@netfilter.org> wrote:
> BTW, the atomic chain notifier in IPv6 seems to be there to handle
> this update from the packet path:
> 
>  ndisc_rcv()
>  ndisc_router_discovery()
>  addrconf_prefix_rcv()
>  manage_tempaddrs()
>  ipv6_add_addr()
>  inet6addr_notifier_call_chain()
> 
> Probably we can get Hannes have a look into this, I think we can
> convert this chain to blocking one through workqueue since
> addrconf_prefix_rcv() returns void. The remaining call sites of
> inet6addr_notifier_call_chain() that I could tracked come from paths
> where I can see ASSERT_RTNL(), so user context is guaranteed.
>
> I'm telling this become I remember that we discussed in netconf'14
> Chicago that it would be good to get rid of this kind og asymmetries
> between IPv4 and IPv6.

Ok, I agree, that would be a lot nicer.

I'll have a look.

  reply	other threads:[~2015-12-11 17:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-09 17:30 [PATCH nf] netfilter: conntrack: resched in nf_ct_iterate_cleanup Florian Westphal
2015-12-11 11:42 ` Pablo Neira Ayuso
2015-12-11 11:53   ` Florian Westphal
2015-12-11 14:43 ` Florian Westphal
2015-12-11 17:16   ` Pablo Neira Ayuso
2015-12-11 17:21     ` Florian Westphal [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-01-20 10:16 Florian Westphal
2016-02-01 17:38 ` Pablo Neira Ayuso

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20151211172123.GA12854@breakpoint.cc \
    --to=fw@strlen.de \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=pablo@netfilter.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.