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)
Wed, Apr 30, 4:50 AM
Unknown Object (File)
Sun, Apr 27, 2:23 AM
Unknown Object (File)
Apr 20 2025, 5:11 AM
Unknown Object (File)
Apr 20 2025, 5:11 AM
Unknown Object (File)
Apr 20 2025, 1:12 AM
Unknown Object (File)
Apr 18 2025, 11:06 AM
Unknown Object (File)
Apr 18 2025, 4:51 AM
Unknown Object (File)
Apr 16 2025, 9:39 PM
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