summaryrefslogtreecommitdiffstats
path: root/sys/dev/pci/drm/amd/amdgpu/amdgpu_gem.c
diff options
context:
space:
mode:
authorclaudio <claudio@openbsd.org>2020-06-22 09:45:13 +0000
committerclaudio <claudio@openbsd.org>2020-06-22 09:45:13 +0000
commit2646c3b95731d186ec4b1bff5cd3c1458c6f5139 (patch)
tree5b4752cdc95dd0c52844b47c4d2cea13338c5a6a /sys/dev/pci/drm/amd/amdgpu/amdgpu_gem.c
parentgup: document and work around "COW can break either way" issue (diff)
downloadwireguard-openbsd-2646c3b95731d186ec4b1bff5cd3c1458c6f5139.tar.xz
wireguard-openbsd-2646c3b95731d186ec4b1bff5cd3c1458c6f5139.zip
The interface if_ioctl routine must be called with the NET_LOCK() held.
For example the bridge_ioctl() function calls NET_UNLOCK() unconditionally and so calling if_ioctl() without netlock will trigger an assert because of not holding the netlock. Make sure the ioctl handlers are called with the netlock held and drop the lock for the wg(4) specific ioctls in the wg_ioctl handler. This fixes a panic in bridge_ioctl() triggered by ifconfig(8) issuing a SIOCGWG ioctl against bridge(4). This is just a workaround this needs more cleanup but at least this way the panic can not be triggered anymore. OK stsp@, tested by semarie@
Diffstat (limited to 'sys/dev/pci/drm/amd/amdgpu/amdgpu_gem.c')
0 files changed, 0 insertions, 0 deletions