Re: bridge_output() and KERNEL_LOCK

2015-12-04 Thread Mark Kettenis
> Date: Fri, 4 Dec 2015 11:48:57 +0100 > From: Martin Pieuchot > > Now that if_start() will take the KERNEL_LOCK itself if the driver is > not marked as IFXF_MPSAFE if_enqueue() is almost mpsafe. > > The missing piece is addressed by the diff below. We want to ensure > bridge_output() is calle

Re: bridge_output() and KERNEL_LOCK

2015-12-04 Thread David Gwynne
ok > On 4 Dec 2015, at 8:48 PM, Martin Pieuchot wrote: > > Now that if_start() will take the KERNEL_LOCK itself if the driver is > not marked as IFXF_MPSAFE if_enqueue() is almost mpsafe. > > The missing piece is addressed by the diff below. We want to ensure > bridge_output() is called with

bridge_output() and KERNEL_LOCK

2015-12-04 Thread Martin Pieuchot
Now that if_start() will take the KERNEL_LOCK itself if the driver is not marked as IFXF_MPSAFE if_enqueue() is almost mpsafe. The missing piece is addressed by the diff below. We want to ensure bridge_output() is called with the KERNEL_LOCK() held. ok? Index: net/if.c