Advanced Micro Devices Inc (AMD)

[dacaw]

Well let's make that clear. Its not applications that pass NX-protected addresses into the kernel, we're only talikng about drivers that execute from an NX-protected buffer or stack. Thus there's only ONE driver that does this?? Mpegport.sys. That's amazing. All of the Win3.1 graphics drivers wrote code on the stack, it was part of the reference DDK. Plus it seems that the fault lies in the initialization code, only called at startup. I would think that run-time code would have the illegal access trapped.

This whole thing is a NON-ISSUE. It applies to just ONE driver. If an app passes an NX callback to the kernel it will NOT prompt for a reboot any more than if an illegal address were passed