From: Stephen Hemminger <stephen@networkplumber.org>
To: David Miller <davem@davemloft.net>
Cc: jtluka@redhat.com, jiri@resnulli.us, mst@redhat.com,
netdev@vger.kernel.org, bridge@lists.linux-foundation.org,
edumazet@google.com, laine@redhat.com, zhiguohong@tencent.com
Subject: Re: [Bridge] [patch net/stable v2] br: fix use of ->rx_handler_data in code executed on non-rx_handler path
Date: Fri, 6 Dec 2013 13:10:28 -0800 [thread overview]
Message-ID: <20131206131028.41b5b8b1@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <20131206.154321.1673089712073824539.davem@davemloft.net>
On Fri, 06 Dec 2013 15:43:21 -0500 (EST)
David Miller <davem@davemloft.net> wrote:
> From: Jiri Pirko <jiri@resnulli.us>
> Date: Thu, 5 Dec 2013 16:27:37 +0100
>
> > br_stp_rcv() is reached by non-rx_handler path. That means there is no
> > guarantee that dev is bridge port and therefore simple NULL check of
> > ->rx_handler_data is not enough. There is need to check if dev is really
> > bridge port and since only rcu read lock is held here, do it by checking
> > ->rx_handler pointer.
> >
> > Note that synchronize_net() in netdev_rx_handler_unregister() ensures
> > this approach as valid.
> >
> > Introduced originally by:
> > commit f350a0a87374418635689471606454abc7beaa3a
> > "bridge: use rx_handler_data pointer to store net_bridge_port pointer"
> >
> > Fixed but not in the best way by:
> > commit b5ed54e94d324f17c97852296d61a143f01b227a
> > "bridge: fix RCU races with bridge port"
> >
> > Reintroduced by:
> > commit 716ec052d2280d511e10e90ad54a86f5b5d4dcc2
> > "bridge: fix NULL pointer deref of br_port_get_rcu"
> >
> > Please apply to stable trees as well. Thanks.
> >
> > RH bugzilla reference: https://bugzilla.redhat.com/show_bug.cgi?id=1025770
> >
> > Reported-by: Laine Stump <laine@redhat.com>
> > Debugged-by: Michael S. Tsirkin <mst@redhat.com>
> > Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
> > Signed-off-by: Jiri Pirko <jiri@resnulli.us>
> > ---
> > v1->v2: moved br_port_get_check_rcu definition below br_handle_frame definition
>
> Applied and queued up for -stable, thanks Jiri.
How come you ignored my simpler fix, that used the existing logic.
I don't like introducing this especially into the stable; much prefer
to go back to testing the flag as was being done before.
next prev parent reply other threads:[~2013-12-06 21:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-05 15:27 [Bridge] [patch net/stable v2] br: fix use of ->rx_handler_data in code executed on non-rx_handler path Jiri Pirko
2013-12-05 15:35 ` Michael S. Tsirkin
2013-12-05 15:37 ` Eric Dumazet
2013-12-05 16:55 ` Stephen Hemminger
2013-12-06 2:26 ` Gao feng
2013-12-07 1:44 ` Vlad Yasevich
2013-12-06 20:43 ` David Miller
2013-12-06 21:10 ` Stephen Hemminger [this message]
2013-12-06 21:16 ` David Miller
2013-12-07 8:51 ` Jiri Pirko
2013-12-07 17:42 ` Stephen Hemminger
2013-12-07 18:18 ` Jiri Pirko
2013-12-07 19:10 ` Vlad Yasevich
2013-12-07 20:07 ` Jiri Pirko
2013-12-09 2:07 ` Vlad Yasevich
2013-12-09 9:36 ` Jiri Pirko
2013-12-09 11:58 ` Michael S. Tsirkin
2013-12-09 12:13 ` Jiri Pirko
2013-12-09 19:31 ` Vlad Yasevich
2013-12-09 21:52 ` Jiri Pirko
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=20131206131028.41b5b8b1@nehalam.linuxnetplumber.net \
--to=stephen@networkplumber.org \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jiri@resnulli.us \
--cc=jtluka@redhat.com \
--cc=laine@redhat.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=zhiguohong@tencent.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