aboutsummaryrefslogtreecommitdiff
path: root/lib/test_fortify/write_overflow_field-memcpy.c
diff options
context:
space:
mode:
authorMark Brown <[email protected]>2023-05-22 15:28:00 +0100
committerCatalin Marinas <[email protected]>2023-05-26 10:22:03 +0100
commitcb5aa637943857f7f937a51d1e621dbe925f9f67 (patch)
tree70b512a9f636814a515d93f0a62fcb105c2137d1 /lib/test_fortify/write_overflow_field-memcpy.c
parent44c026a73be8038f03dbdeef028b642880cf1511 (diff)
kselftest/arm64: Add a smoke test for ptracing hardware break/watch points
There was a report that the hardware breakpoints and watch points weren't reporting the debug architecture version as expected, they were reporting a version of 0 which is not defined in the architecture. This happens when running in a KVM guest if the host has a debug architecture version not supported by KVM, it in turn confuses GDB which rejects any debug architecture version it does not know about. Add a test that covers that situation and while we're at it reports the debug architecture version and number of slots available to aid with figuring out problems that may arise. Signed-off-by: Mark Brown <[email protected]> Link: https://lore.kernel.org/r/[email protected] Signed-off-by: Catalin Marinas <[email protected]>
Diffstat (limited to 'lib/test_fortify/write_overflow_field-memcpy.c')
0 files changed, 0 insertions, 0 deletions