From: Christoph Hellwig <hch@infradead.org>
To: Mika Kuoppala <mika.kuoppala@linux.intel.com>
Cc: intel-xe@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
christian.koenig@amd.com, Oleg Nesterov <oleg@redhat.com>,
linux-kernel@vger.kernel.org, Dave Airlie <airlied@redhat.com>,
Lucas De Marchi <lucas.demarchi@intel.com>,
Matthew Brost <matthew.brost@intel.com>,
Andi Shyti <andi.shyti@intel.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Maciej Patelczyk <maciej.patelczyk@linux.intel.com>,
Dominik Grzegorzek <dominik.grzegorzek@intel.com>,
Jonathan Cavitt <jonathan.cavitt@intel.com>,
Andi Shyti <andi.shyti@linux.intel.com>
Subject: Re: [PATCH 01/26] ptrace: export ptrace_may_access
Date: Mon, 9 Dec 2024 20:29:38 -0800 [thread overview]
Message-ID: <Z1fDsvIKB4j_-Tv_@infradead.org> (raw)
In-Reply-To: <20241209133318.1806472-2-mika.kuoppala@linux.intel.com>
On Mon, Dec 09, 2024 at 03:32:52PM +0200, Mika Kuoppala wrote:
> xe driver would like to allow fine grained access control
> for GDB debugger using ptrace. Without this export, the only
> option would be to check for CAP_SYS_ADMIN.
>
> The check intended for an ioctl to attach a GPU debugger
> is similar to the ptrace use case: allow a calling process
> to manipulate a target process if it has the necessary
> capabilities or the same permissions, as described in
> Documentation/process/adding-syscalls.rst.
>
> Export ptrace_may_access function to allow GPU debugger to
> have identical access control for debugger(s)
> as a CPU debugger.
This seems to mis an actual user or you forgot to Cc linux-kernel on it.
next prev parent reply other threads:[~2024-12-10 4:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241209133318.1806472-1-mika.kuoppala@linux.intel.com>
2024-12-09 13:32 ` [PATCH 01/26] ptrace: export ptrace_may_access Mika Kuoppala
2024-12-10 4:29 ` Christoph Hellwig [this message]
2024-12-12 9:16 ` Joonas Lahtinen
[not found] ` <20241209133318.1806472-15-mika.kuoppala@linux.intel.com>
2024-12-09 14:03 ` [PATCH 14/26] drm/xe/eudebug: implement userptr_vma access Christian König
2024-12-09 14:56 ` Joonas Lahtinen
2024-12-09 15:31 ` Simona Vetter
2024-12-09 15:42 ` Christian König
2024-12-09 15:45 ` Christian König
2024-12-10 9:33 ` Joonas Lahtinen
[not found] ` <d2141daa-b556-4487-a310-69a7fea4eae8@amd.com>
2024-12-10 11:57 ` Joonas Lahtinen
[not found] ` <bbe0193c-8869-488a-ae23-139a244654c8@amd.com>
2024-12-11 12:59 ` Joonas Lahtinen
2024-12-17 14:12 ` Joonas Lahtinen
2024-12-20 12:47 ` Mika Kuoppala
2024-12-10 11:17 ` Simona Vetter
2024-12-12 8:49 ` Thomas Hellström
2024-12-12 10:12 ` Simona Vetter
2024-12-13 19:39 ` Matthew Brost
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=Z1fDsvIKB4j_-Tv_@infradead.org \
--to=hch@infradead.org \
--cc=airlied@redhat.com \
--cc=andi.shyti@intel.com \
--cc=andi.shyti@linux.intel.com \
--cc=christian.koenig@amd.com \
--cc=dominik.grzegorzek@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jonathan.cavitt@intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lucas.demarchi@intel.com \
--cc=maciej.patelczyk@linux.intel.com \
--cc=matthew.brost@intel.com \
--cc=mika.kuoppala@linux.intel.com \
--cc=oleg@redhat.com \
/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