having a tough time explaining people that no, even if there's a component referred to as a "driver" inside, a piece of userspace software can not ultimately be at fault for a kernel panic
-
yeah, if you really try you can come up with all sorts of ways to do it, sure here, the issue is "the machine reboots", so you could just straight-up write 'b' to /proc/sysrq-trigger if you had the right perms
Admittedly if you do any of those you're definitely getting exactly what you asked for. Didn't stop me from writing a userspace device tool that sets up DMA to a hugepage mapped from userspace though. Sadly, not IOMMU-compatible.