Page MenuHomeFreeBSD

arm64: Raise a SIGBUS on a user external abort
ClosedPublic

Authored by andrew on Sep 29 2023, 1:59 PM.
Tags
None
Referenced Files
Unknown Object (File)
Tue, Jun 9, 9:35 AM
Unknown Object (File)
Fri, Jun 5, 11:06 PM
Unknown Object (File)
Sun, May 31, 8:54 PM
Unknown Object (File)
Sun, May 31, 2:20 PM
Unknown Object (File)
Sun, May 31, 2:02 PM
Unknown Object (File)
Thu, May 28, 8:29 PM
Unknown Object (File)
Mon, May 18, 8:32 AM
Unknown Object (File)
Sat, May 16, 12:27 AM
Subscribers

Details

Summary

When userspace triggers an external abort allow it to handle the abort
by raising a SIGBUS.

Sponsored by: Arm Ltd

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

sys/arm64/arm64/trap.c
230

Does this mean that userspace can't reliably distinguish between a SIGBUS due to a vm_fault() failure and a SIGBUS due to an external abort?

239

No need to test !lower now.

246

Same here.

Remove unneeded lower checks

sys/arm64/arm64/trap.c
230

The app gets the fault address from FAR, which should be enough for it to understand the specific mapping that caused the trap.

In other words, I think that there is no need for additional arch-specific BUS_XXX code for this situation.

This revision is now accepted and ready to land.Oct 11 2023, 5:38 PM