From: "Christian König" <ckoenig.leichtzumerken@gmail.com>
To: Simon Ser <contact@emersion.fr>,
Pierre-Eric Pelloux-Prayer <pierre-eric.pelloux-prayer@amd.com>
Cc: Shashank Sharma <shashank.sharma@amd.com>,
Amaranath Somalapuram <amaranath.somalapuram@amd.com>,
amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
Alexandar Deucher <alexander.deucher@amd.com>,
Shashank Sharma <contactshashanksharma@gmail.com>,
Christian Koenig <christian.koenig@amd.com>
Subject: Re: [PATCH v2 1/2] drm: Add GPU reset sysfs event
Date: Wed, 9 Mar 2022 11:24:02 +0100 [thread overview]
Message-ID: <1e2ad919-e336-cf8f-c675-0ddd62796a0f@gmail.com> (raw)
In-Reply-To: <DQGKSkEjxg-p9oBYX3hMa6fmY3Am2mAT4KBSQL_qsLGK0m85wehKp54s1IbobLSc5-FGbY67HrlWfQYO876bGgeObzY5eJF5UXJ1BktPilA=@emersion.fr>
Am 09.03.22 um 11:10 schrieb Simon Ser:
> On Wednesday, March 9th, 2022 at 10:56, Pierre-Eric Pelloux-Prayer <pierre-eric.pelloux-prayer@amd.com> wrote:
>
>> Would it be possible to include the app parameters as well?
> Can all processes read sysfs events?
No, but application parameters are usually not secret.
> There might be security implications here. The app parameters might
> contain sensitive information, like passwords or tokens.
It's a well known security vulnerably to provide password etc.. as
application parameter since everybody can read them through procfs.
> Can't the uevent receiver query the kernel to get that info from the
> PID?
I'm leaning also towards just providing the PID and not the application
name. The information should be as short as possible.
Regards,
Christian.
next prev parent reply other threads:[~2022-03-09 10:24 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-08 18:04 [PATCH v2 1/2] drm: Add GPU reset sysfs event Shashank Sharma
2022-03-08 18:04 ` [PATCH v2 2/2] drm/amdgpu: add work function for GPU reset event Shashank Sharma
2022-03-09 7:47 ` [PATCH v2 1/2] drm: Add GPU reset sysfs event Simon Ser
2022-03-09 11:18 ` Sharma, Shashank
2022-03-09 8:09 ` Christian König
2022-03-09 9:56 ` Pierre-Eric Pelloux-Prayer
2022-03-09 10:10 ` Simon Ser
2022-03-09 10:24 ` Christian König [this message]
2022-03-09 10:28 ` Simon Ser
2022-03-09 10:28 ` Pierre-Eric Pelloux-Prayer
2022-03-09 18:12 ` Rob Clark
2022-03-10 9:55 ` Christian König
2022-03-10 15:24 ` Rob Clark
2022-03-10 16:21 ` Sharma, Shashank
2022-03-10 16:27 ` Andrey Grodzovsky
2022-03-10 17:16 ` Rob Clark
2022-03-10 17:10 ` Rob Clark
2022-03-10 17:19 ` Sharma, Shashank
2022-03-10 17:40 ` Rob Clark
2022-03-10 18:33 ` Abhinav Kumar
2022-03-10 19:14 ` Sharma, Shashank
2022-03-10 19:35 ` Rob Clark
2022-03-10 19:44 ` Sharma, Shashank
2022-03-10 19:56 ` Rob Clark
2022-03-10 20:17 ` Sharma, Shashank
2022-03-11 8:30 ` Pekka Paalanen
2022-03-14 14:23 ` Alex Deucher
2022-03-14 15:26 ` Pekka Paalanen
2022-03-15 14:54 ` Alex Deucher
2022-03-16 8:48 ` Pekka Paalanen
2022-03-16 14:12 ` Alex Deucher
2022-03-16 15:36 ` Rob Clark
2022-03-16 15:48 ` Alex Deucher
2022-03-16 16:30 ` Rob Clark
2022-03-17 7:03 ` Christian König
2022-03-17 9:29 ` Daniel Vetter
2022-03-17 9:46 ` Christian König
2022-03-17 15:34 ` Rob Clark
2022-03-17 17:23 ` Daniel Vetter
2022-03-17 15:40 ` Rob Clark
2022-03-17 17:26 ` Daniel Vetter
2022-03-17 17:31 ` Rob Clark
2022-03-18 7:42 ` Christian König
2022-03-18 15:12 ` Rob Clark
2022-03-21 9:30 ` Christian König
2022-03-21 16:03 ` Rob Clark
2022-03-23 14:07 ` Daniel Stone
2022-03-23 15:14 ` Daniel Vetter
2022-03-23 15:25 ` Christian König
2022-03-26 0:53 ` Olsak, Marek
2022-03-29 12:14 ` Christian König
2022-03-29 16:25 ` Marek Olšák
2022-03-30 9:49 ` Daniel Vetter
2022-03-23 17:30 ` Rob Clark
2022-03-21 14:15 ` Daniel Vetter
2022-03-15 7:13 ` Dave Airlie
2022-03-15 7:25 ` Simon Ser
2022-03-15 7:25 ` Christian König
2022-03-17 9:25 ` Daniel Vetter
2022-03-16 21:50 ` Rob Clark
2022-03-17 8:42 ` Sharma, Shashank
2022-03-17 9:21 ` Christian König
2022-03-17 10:31 ` Daniel Stone
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=1e2ad919-e336-cf8f-c675-0ddd62796a0f@gmail.com \
--to=ckoenig.leichtzumerken@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amaranath.somalapuram@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=contact@emersion.fr \
--cc=contactshashanksharma@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=pierre-eric.pelloux-prayer@amd.com \
--cc=shashank.sharma@amd.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;
as well as URLs for NNTP newsgroup(s).