[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Z1fDsvIKB4j_-Tv_@infradead.org>
Date: Mon, 9 Dec 2024 20:29:38 -0800
From: Christoph Hellwig <hch@...radead.org>
To: Mika Kuoppala <mika.kuoppala@...ux.intel.com>
Cc: intel-xe@...ts.freedesktop.org, dri-devel@...ts.freedesktop.org,
christian.koenig@....com, Oleg Nesterov <oleg@...hat.com>,
linux-kernel@...r.kernel.org, Dave Airlie <airlied@...hat.com>,
Lucas De Marchi <lucas.demarchi@...el.com>,
Matthew Brost <matthew.brost@...el.com>,
Andi Shyti <andi.shyti@...el.com>,
Joonas Lahtinen <joonas.lahtinen@...ux.intel.com>,
Maciej Patelczyk <maciej.patelczyk@...ux.intel.com>,
Dominik Grzegorzek <dominik.grzegorzek@...el.com>,
Jonathan Cavitt <jonathan.cavitt@...el.com>,
Andi Shyti <andi.shyti@...ux.intel.com>
Subject: Re: [PATCH 01/26] ptrace: export ptrace_may_access
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.
Powered by blists - more mailing lists