From: Osama Abdelkader <osama.abdelkader@gmail.com>
To: Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
linux-arm-kernel@lists.infradead.org,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Osama Abdelkader <osama.abdelkader@gmail.com>
Subject: [PATCH v2] arm64: hw_breakpoint: warn on invalid breakpoint length
Date: Sat, 13 Dec 2025 12:23:35 +0100 [thread overview]
Message-ID: <20251213112336.26503-1-osama.abdelkader@gmail.com> (raw)
Some tools (e.g. perf) incorrectly assume that breakpoints should be
sizeof(long), but this is wrong for AArch64 where breakpoints must be
4 bytes. Add a warning when we silently fix up the parameter so tool
developers can get notified.
This addresses the FIXME comment by adding diagnostic output rather
than breaking existing tools by returning -EINVAL.
Signed-off-by: Osama Abdelkader <osama.abdelkader@gmail.com>
---
v2: fix warning messageline splitting
---
arch/arm64/kernel/hw_breakpoint.c | 10 ++++++----
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git a/arch/arm64/kernel/hw_breakpoint.c b/arch/arm64/kernel/hw_breakpoint.c
index ab76b36dce82..cce306145d78 100644
--- a/arch/arm64/kernel/hw_breakpoint.c
+++ b/arch/arm64/kernel/hw_breakpoint.c
@@ -475,11 +475,13 @@ static int arch_build_bp_info(struct perf_event *bp,
return -EINVAL;
} else if (hw->ctrl.len != ARM_BREAKPOINT_LEN_4) {
/*
- * FIXME: Some tools (I'm looking at you perf) assume
- * that breakpoints should be sizeof(long). This
- * is nonsense. For now, we fix up the parameter
- * but we should probably return -EINVAL instead.
+ * Some tools (e.g. perf) incorrectly assume that
+ * breakpoints should be sizeof(long). This is wrong
+ * for AArch64 where breakpoints must be 4 bytes.
+ * Warn the user and fix up the parameter.
*/
+ pr_warn_once("hw_breakpoint: invalid AArch64 breakpoint length %d, fixing to 4 bytes\n",
+ hw->ctrl.len);
hw->ctrl.len = ARM_BREAKPOINT_LEN_4;
}
}
--
2.43.0
next reply other threads:[~2025-12-13 11:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-13 11:23 Osama Abdelkader [this message]
2025-12-15 14:59 ` [PATCH v2] arm64: hw_breakpoint: warn on invalid breakpoint length Leo Yan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20251213112336.26503-1-osama.abdelkader@gmail.com \
--to=osama.abdelkader@gmail.com \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=will@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).