summaryrefslogtreecommitdiffstats
path: root/lib/libkvm/kvm_proc.c
diff options
context:
space:
mode:
authorbluhm <bluhm@openbsd.org>2016-05-22 20:27:04 +0000
committerbluhm <bluhm@openbsd.org>2016-05-22 20:27:04 +0000
commit9ee302b807409cb1f9713adc404a77fe222e525c (patch)
treeaa5fe5ae4375c8135911855d360673c191e7e222 /lib/libkvm/kvm_proc.c
parentmakes sure the value of the asprintf buffer is zeroed on error (diff)
downloadwireguard-openbsd-9ee302b807409cb1f9713adc404a77fe222e525c.tar.xz
wireguard-openbsd-9ee302b807409cb1f9713adc404a77fe222e525c.zip
When pulling an msdos formated umass stick during mount while the
usb stack was busy, the kernel could trigger an uvm fault. There is a race between vop_generic_revoke() and sys_mount() where vgonel() could reset v_specinfo. Then v_specmountpoint is no longer valid. So after sleeping, msdosfs_mountfs() could crash in the error path. The code in the different *_mountfs() functions was inconsistent, implement the same check everywhere. OK krw@ natano@
Diffstat (limited to 'lib/libkvm/kvm_proc.c')
0 files changed, 0 insertions, 0 deletions