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)
Sat, Jun 28, 9:03 AM
Unknown Object (File)
Fri, Jun 27, 3:50 AM
Unknown Object (File)
Thu, Jun 26, 5:25 AM
Unknown Object (File)
Thu, Jun 26, 3:17 AM
Unknown Object (File)
Wed, Jun 25, 2:46 PM
Unknown Object (File)
Tue, Jun 24, 9:31 AM
Unknown Object (File)
Sun, Jun 22, 2:05 AM
Unknown Object (File)
May 30 2025, 12:09 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