[PATCH] net/bridge/br_if.c: fix possible use-after-free in port_carrier_check() · Oleg Nesterov <hidden> · 2007-02-20
Re: [PATCH] net/bridge/br_if.c: fix possible use-after-free in port_carrier_check() · Stephen Hemminger <hidden> · 2007-02-21
Re: [PATCH] net/bridge/br_if.c: fix possible use-after-free in port_carrier_check() · Jarek Poplawski <hidden> · 2007-02-21
Re: [PATCH] net/bridge/br_if.c: fix possible use-after-free in port_carrier_check() · Jarek Poplawski <hidden> · 2007-02-21
Re: [PATCH] net/bridge/br_if.c: fix possible use-after-free in port_carrier_check() · Oleg Nesterov <hidden> · 2007-02-21
[RFT] bridge: eliminate port_check workqueue · Stephen Hemminger <hidden> · 2007-02-21
Re: [RFT] bridge: eliminate port_check workqueue · Oleg Nesterov <hidden> · 2007-02-21
Re: [RFT] bridge: eliminate port_check workqueue · Stephen Hemminger <hidden> · 2007-02-21
Re: [RFT] bridge: eliminate port_check workqueue · Oleg Nesterov <hidden> · 2007-02-21
Re: [RFT] bridge: eliminate port_check workqueue · Jarek Poplawski <hidden> · 2007-02-22
Re: [PATCH] net/bridge/br_if.c: fix possible use-after-free in port_carrier_check() · Oleg Nesterov <hidden> · 2007-02-21

Re: [PATCH] net/bridge/br_if.c: fix possible use-after-free in port_carrier_check()

From: Jarek Poplawski <hidden>
Date: 2007-02-21 09:26:11
Also in: lkml

On Wed, Feb 21, 2007 at 09:23:45AM +0100, Jarek Poplawski wrote:
...

I have known issues with RCU, but dare to disagree here.
It's done during call_rcu, so anything RCU friendly shouldn't
see this at the moment at all. It could be needed for those
with refcounting - than it should be checked, if there is
anything more than port_carrier_check.

Sorry for this than-ing!
(It's my next favorite issue after RCU.)

Jarek P.

`h`	back out one level
`j`	next message in thread
`k`	previous message in thread
`l`	drill in
`Esc`	close help / fold thread tree
`?`	toggle this help