[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20131018111041.GA10964@localhost>
Date: Fri, 18 Oct 2013 13:10:41 +0200
From: Pablo Neira Ayuso <pablo@...filter.org>
To: Antonio Quartulli <antonio@...n-mesh.com>
Cc: Antonio Quartulli <antonio@...hcoding.com>,
"David S. Miller" <davem@...emloft.net>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
Stephen Hemminger <stephen@...workplumber.org>
Subject: Re: [PATCH net] bridge: clean the nf_bridge status when forwarding
the skb
On Thu, Oct 17, 2013 at 01:37:35PM +0200, Antonio Quartulli wrote:
> On Thu, Oct 17, 2013 at 04:28:57AM -0700, Pablo Neira Ayuso wrote:
> > Hi,
> > > +
> > > +/**
> > > + * br_netfilter_skb_free - clean the NF bridge data in an skb
> > > + * @skb: the skb which the data to free belongs to
> > > + */
> > > +void br_netfilter_skb_free(struct sk_buff *skb)
> > > +{
> > > + nf_bridge_put(skb->nf_bridge);
> > > + skb->nf_bridge = NULL;
> > > +}
> >
> > This should be nf_reset.
>
> You think I should directly use nf_reset instead of this function?
>
> I see that nf_reset() cleans up the conntrack part too: does it also become
> useless once the packet exits the bridge interface?
The conntrack should not attached if it's forwarded to another netif,
see dev_forward_skb.
But I'm not sure what scenario you're trying to handle with this
change, if you could please elaborate.
Perhaps your fix is more conservative to avoid breaking strange setups
that have been relying on this behaviour. I know of people deploying
strange configurations using netfilter bridge.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists