diff options
author | Di Zhu <zhudi21@huawei.com> | 2021-04-19 16:56:41 +0300 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2021-04-20 02:08:03 +0300 |
commit | c1102e9d49eb36c0be18cb3e16f6e46ffb717964 (patch) | |
tree | e481fbf34deb6cf8e86159fd373bc8314e0771f4 /net/8021q/vlan_mvrp.c | |
parent | 7ad18ff6449cbd6beb26b53128ddf56d2685aa93 (diff) | |
download | linux-c1102e9d49eb36c0be18cb3e16f6e46ffb717964.tar.xz |
net: fix a data race when get vlan device
We encountered a crash: in the packet receiving process, we got an
illegal VLAN device address, but the VLAN device address saved in vmcore
is correct. After checking the code, we found a possible data
competition:
CPU 0: CPU 1:
(RCU read lock) (RTNL lock)
vlan_do_receive() register_vlan_dev()
vlan_find_dev()
->__vlan_group_get_device() ->vlan_group_prealloc_vid()
In vlan_group_prealloc_vid(), We need to make sure that memset()
in kzalloc() is executed before assigning value to vlan devices array:
=================================
kzalloc()
->memset(object, 0, size)
smp_wmb()
vg->vlan_devices_arrays[pidx][vidx] = array;
==================================
Because __vlan_group_get_device() function depends on this order.
otherwise we may get a wrong address from the hardware cache on
another cpu.
So fix it by adding memory barrier instruction to ensure the order
of memory operations.
Signed-off-by: Di Zhu <zhudi21@huawei.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/8021q/vlan_mvrp.c')
0 files changed, 0 insertions, 0 deletions