diff options
| author | martin <martin@NetBSD.org> | 2020-04-27 14:56:22 +0000 |
|---|---|---|
| committer | martin <martin@NetBSD.org> | 2020-04-27 14:56:22 +0000 |
| commit | 8fbdf1123ffdc42ec06ddc4500d925c5be272b0f (patch) | |
| tree | b5c1d5ecb0423e7def2bc2d47362f6017b295551 /sys/dev/microcode | |
| parent | 9f0a2632f62ae4dfe847324dc14b313d2361f689 (diff) | |
Pull up following revision(s) (requested by maxv in ticket #857):
sys/dev/nvmm/nvmm.c: revision 1.26
In nvmm_open(), make sure an implementation was found. This fixes an
initialization bug triggerable in certain conditions.
If you build nvmm inside the kernel, AND have a cpu that is not supported,
AND run nvmmctl (or qemu-nvmm, both being the only binaries in the "nvmm"
group), you get a page fault.
This is because when nvmm is built inside the kernel, the kernel registers
nvmm_cdevsw behind nvmm's back. The ioctl is therefore always accessible,
and will hit NULL pointers if nvmm_init() failed.
Problem reported by Andrei M. on netbsd-users@, thanks.
Diffstat (limited to 'sys/dev/microcode')
0 files changed, 0 insertions, 0 deletions
