From: Shmulik Ladkani <shmulik.ladkani@gmail.com>
To: Ido Schimmel <idosch@mellanox.com>
Cc: <stephen@networkplumber.org>, <davem@davemloft.net>,
<bridge@lists.linux-foundation.org>, <netdev@vger.kernel.org>,
<eladr@mellanox.com>, <ogerlitz@mellanox.com>,
<jiri@mellanox.com>, <yotamg@mellanox.com>, <nogahf@mellanox.com>,
Florian Westphal <fw@strlen.de>
Subject: Re: [PATCH net] bridge: Fix incorrect re-injection of STP packets
Date: Sat, 4 Jun 2016 09:41:41 +0300 [thread overview]
Message-ID: <20160604094141.7dcc5687@halley> (raw)
In-Reply-To: <1464946785-7651-1-git-send-email-idosch@mellanox.com>
Hi,
On Fri, 3 Jun 2016 12:39:45 +0300 Ido Schimmel <idosch@mellanox.com> wrote:
> diff --git a/net/bridge/br_input.c b/net/bridge/br_input.c
> index 1607977..c73ed44 100644
> --- a/net/bridge/br_input.c
> +++ b/net/bridge/br_input.c
> @@ -223,9 +223,7 @@ static int br_handle_local_finish(struct net *net, struct sock *sk, struct sk_bu
> if (p->flags & BR_LEARNING && br_should_learn(p, skb, &vid))
> br_fdb_update(p->br, p, eth_hdr(skb)->h_source, vid, false);
>
> - BR_INPUT_SKB_CB(skb)->brdev = p->br->dev;
> - br_pass_frame_up(skb);
> - return 0;
> + return RX_HANDLER_PASS;
> }
>
> /*
> @@ -238,6 +236,7 @@ rx_handler_result_t br_handle_frame(struct sk_buff **pskb)
> struct sk_buff *skb = *pskb;
> const unsigned char *dest = eth_hdr(skb)->h_dest;
> br_should_route_hook_t *rhook;
> + int err;
>
> if (unlikely(skb->pkt_type == PACKET_LOOPBACK))
> return RX_HANDLER_PASS;
> @@ -287,8 +286,11 @@ rx_handler_result_t br_handle_frame(struct sk_buff **pskb)
> }
>
> /* Deliver packet to local host only */
> - NF_HOOK(NFPROTO_BRIDGE, NF_BR_LOCAL_IN, dev_net(skb->dev),
> - NULL, skb, skb->dev, NULL, br_handle_local_finish);
> + err = NF_HOOK(NFPROTO_BRIDGE, NF_BR_LOCAL_IN, dev_net(skb->dev),
> + NULL, skb, skb->dev, NULL,
> + br_handle_local_finish);
> + if (err == RX_HANDLER_PASS)
> + return RX_HANDLER_PASS;
> return RX_HANDLER_CONSUMED;
Seems '*pskb = skb' is needed prior returning RX_HANDLER_PASS - there's
a 'skb = skb_share_check()' at beginning of br_handle_frame.
(The *pskb = skb was present prior 8626c56c8279, but gone since there
was no longer an RX_HANDLER_PASS return).
One nit to consider:
The fix relies on the fact that RX_HANDLER_PASS != 0 (otherwise we end up
not knowing whether skb was STOLEN or br_handle_local_finish has
executed, which was the original problem 8626c56c8279 tried to address).
No reason to use the RX_HANDLER_xxx enumeration space as the ret code
of an 'okfn' (br_handle_local_finish in this case).
Some positive value locally defined in br_input.c (and documented in
br_handle_local_finish) would do.
Regards,
Shmulik
next prev parent reply other threads:[~2016-06-04 6:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-03 9:39 [PATCH net] bridge: Fix incorrect re-injection of STP packets Ido Schimmel
2016-06-04 6:41 ` Shmulik Ladkani [this message]
2016-06-04 8:15 ` Ido Schimmel
2016-06-05 7:40 ` Ido Schimmel
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=20160604094141.7dcc5687@halley \
--to=shmulik.ladkani@gmail.com \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=eladr@mellanox.com \
--cc=fw@strlen.de \
--cc=idosch@mellanox.com \
--cc=jiri@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=nogahf@mellanox.com \
--cc=ogerlitz@mellanox.com \
--cc=stephen@networkplumber.org \
--cc=yotamg@mellanox.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).