From: Oleg Nesterov <oleg@redhat.com>
To: Tiezhu Yang <yangtiezhu@loongson.cn>
Cc: Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Catalin Marinas <catalin.marinas@arm.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] arm64: hw_breakpoint: Save privilege of access control via ptrace
Date: Thu, 20 Jun 2024 12:36:00 +0200 [thread overview]
Message-ID: <20240620103600.GD30070@redhat.com> (raw)
In-Reply-To: <93d96e55-c180-444a-9b3f-f96db5f9e37d@loongson.cn>
Again, I can't really comment, I know almost nothing about perf, but
On 06/20, Tiezhu Yang wrote:
>
> On 06/20/2024 05:08 PM, Oleg Nesterov wrote:
> >
> >But to me the very idea of arm64-specific and "kernel only" member in
> >perf_event_attr looks a bit strange.
>
> I noticed that there is a similar arm64-specific change in
> commit 09519ec3b19e ("perf: Add perf_event_attr::config3")
but this is another thing even if I have no idea what .config3 means.
If nothing else, what do you think, say, tools/perf can do with ->bp_priv?
What should sys_perf_event_open() do if bp_priv != 0 comes from user space?
Nevermind, please forget, I leave this to you and maintainers.
Oleg.
next prev parent reply other threads:[~2024-06-20 10:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-18 7:10 [PATCH] arm64: hw_breakpoint: Save privilege of access control via ptrace Tiezhu Yang
2024-06-19 15:15 ` Oleg Nesterov
2024-06-20 2:05 ` Tiezhu Yang
2024-06-20 9:08 ` Oleg Nesterov
2024-06-20 9:30 ` Will Deacon
2024-06-20 9:50 ` Tiezhu Yang
2024-06-20 10:36 ` Oleg Nesterov [this message]
2024-06-20 11:31 ` James Clark
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=20240620103600.GD30070@redhat.com \
--to=oleg@redhat.com \
--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=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=will@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.