summaryrefslogtreecommitdiffstats
path: root/lib/libusb/libusb10_desc.c
diff options
context:
space:
mode:
authorkib <kib@FreeBSD.org>2009-07-10 10:29:16 +0000
committerkib <kib@FreeBSD.org>2009-07-10 10:29:16 +0000
commitbc06993eb4fc58e6b7b99c857dcdc29054d79d0c (patch)
tree5b8477de1ef13e4111ea0ec3cc2d7374693bc406 /lib/libusb/libusb10_desc.c
parente33e5dce327927280ca13509bde4fac5f9d39fe1 (diff)
downloadFreeBSD-src-bc06993eb4fc58e6b7b99c857dcdc29054d79d0c.zip
FreeBSD-src-bc06993eb4fc58e6b7b99c857dcdc29054d79d0c.tar.gz
When amd64 CPU cannot load segment descriptor during trap return to
usermode, it generates GPF, that is mirrored to user mode as SIGSEGV. The offending register in mcontext should contain the value loading of which generated the GPF, and it is so on i386. On amd64, we currently report segment descriptor in tf_err, while segment register contains the corrected value loaded by trap handler. Fix the issue by behaving like i386, reloading segment register in trap frame after signal frame is pushed onto user stack. Noted and tested by: pho Approved by: re (kensmith)
Diffstat (limited to 'lib/libusb/libusb10_desc.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud