From: Will Deacon <will@kernel.org>
To: Tiezhu Yang <yangtiezhu@loongson.cn>
Cc: Mark Rutland <mark.rutland@arm.com>,
Russell King <linux@armlinux.org.uk>,
Catalin Marinas <catalin.marinas@arm.com>,
Oleg Nesterov <oleg@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 3/3] arm64: hw_breakpoint: Save privilege of access control via ptrace
Date: Tue, 9 Jul 2024 11:05:16 +0100 [thread overview]
Message-ID: <20240709100515.GB12978@willie-the-truck> (raw)
In-Reply-To: <20240709095506.9691-4-yangtiezhu@loongson.cn>
On Tue, Jul 09, 2024 at 05:55:06PM +0800, Tiezhu Yang wrote:
> In the current code, decode_ctrl_reg() saves the privilege of access
> control passed by the ptrace user data, but it is not used anymore,
> arch_build_bp_info() checks whether bp virtual address is in kernel
> space to construct hw->ctrl.privilege, it seems not reasonable.
>
> The value of ctrl->privilege saved in decode_ctrl_reg() can be used
> in arch_build_bp_info(), there is no need to check bp virtual address
> to assign value for hw->ctrl.privilege, just make use of "bp_priv" in
> the struct perf_event_attr to save the privilege of access control via
> ptrace for hardware breakpoint.
>
> Signed-off-by: Tiezhu Yang <yangtiezhu@loongson.cn>
> ---
> arch/arm64/kernel/hw_breakpoint.c | 11 ++---------
> arch/arm64/kernel/ptrace.c | 2 ++
> 2 files changed, 4 insertions(+), 9 deletions(-)
>
> diff --git a/arch/arm64/kernel/hw_breakpoint.c b/arch/arm64/kernel/hw_breakpoint.c
> index 722ac45f9f7b..06e34bcdcf92 100644
> --- a/arch/arm64/kernel/hw_breakpoint.c
> +++ b/arch/arm64/kernel/hw_breakpoint.c
> @@ -486,15 +486,8 @@ static int arch_build_bp_info(struct perf_event *bp,
> /* Address */
> hw->address = attr->bp_addr;
>
> - /*
> - * Privilege
> - * Note that we disallow combined EL0/EL1 breakpoints because
> - * that would complicate the stepping code.
> - */
Just because you remove the comment doesn't mean that constraint no
longer applies.
> - if (arch_check_bp_in_kernelspace(hw))
> - hw->ctrl.privilege = AARCH64_BREAKPOINT_EL1;
> - else
> - hw->ctrl.privilege = AARCH64_BREAKPOINT_EL0;
> + /* Privilege */
> + hw->ctrl.privilege = attr->bp_priv;
>
> /* Enabled? */
> hw->ctrl.enabled = !attr->disabled;
> diff --git a/arch/arm64/kernel/ptrace.c b/arch/arm64/kernel/ptrace.c
> index 0d022599eb61..3b37c4a2e0d4 100644
> --- a/arch/arm64/kernel/ptrace.c
> +++ b/arch/arm64/kernel/ptrace.c
> @@ -309,6 +309,7 @@ static struct perf_event *ptrace_hbp_create(unsigned int note_type,
> attr.bp_addr = 0;
> attr.bp_len = HW_BREAKPOINT_LEN_4;
> attr.bp_type = type;
> + attr.bp_priv = AARCH64_BREAKPOINT_EL0;
> attr.disabled = 1;
>
> bp = register_user_hw_breakpoint(&attr, ptrace_hbptriggered, NULL, tsk);
> @@ -352,6 +353,7 @@ static int ptrace_hbp_fill_attr_ctrl(unsigned int note_type,
> attr->bp_len = len;
> attr->bp_type = type;
> attr->bp_addr += offset;
> + attr->bp_priv = ctrl.privilege;
Wait, so ptrace can now set breakpoints with arbitrary privileges?
Will
next prev parent reply other threads:[~2024-07-09 10:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-09 9:55 [PATCH v3 0/3] hw_breakpoint: Save privilege of access control via ptrace Tiezhu Yang
2024-07-09 9:55 ` [PATCH v3 1/3] perf: Add perf_event_attr::bp_priv Tiezhu Yang
2024-07-09 10:03 ` Will Deacon
2024-07-09 12:05 ` Tiezhu Yang
2024-07-09 9:55 ` [PATCH v3 2/3] arm: hw_breakpoint: Save privilege of access control via ptrace Tiezhu Yang
2024-07-09 9:55 ` [PATCH v3 3/3] arm64: " Tiezhu Yang
2024-07-09 10:05 ` Will Deacon [this message]
2024-07-09 12:07 ` Tiezhu Yang
2024-07-10 12:11 ` Will Deacon
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=20240709100515.GB12978@willie-the-truck \
--to=will@kernel.org \
--cc=acme@kernel.org \
--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=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=yangtiezhu@loongson.cn \
/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