[ovs-dev] [PATCH net-next] net: openvswitch: fix to make sure flow_lookup() is not preempted

Sebastian Andrzej Siewior bigeasy at linutronix.de
Thu Oct 15 07:55:17 UTC 2020

On 2020-10-14 12:44:23 [+0200], Eelco Chaudron wrote:
> Let me know your thoughts.

better. If your seccount is per-CPU then you get away without explicit
writer locking if you rely on global per-CPU locking. You can't do
preempt_disable() because this section can be interrupt by softirq. You
need something stronger :)

Side note: Adding a fixes tag and net-next looks like "stable material
starting next merge window".

> Thanks,
> Eelco


More information about the dev mailing list