search for: br_notify

...ATE_DISABLED state when the lost packet arrived. In fact, the packet is thrown by the bridge because, in br_input.c::br_handle_frame(), state==BR_STATE_DISABLED which force the code to jump to the err: tag at the end of this function. The state is set to this value while an event is received inside br_notify.c::br_device_event(), which do a br_stp_disable_port(). After putting some printk in br_notify.c, i remarked that this event come regularly, and always related to the same bridge port (eth1). It don't hurt me that this event come regularly, but problem is when a packet is flowing in the same ti...