From: Simona Vetter <simona.vetter@ffwll.ch>
To: Jeff Hugo <jeff.hugo@oss.qualcomm.com>
Cc: Simona Vetter <simona.vetter@ffwll.ch>,
DRI Development <dri-devel@lists.freedesktop.org>,
intel-xe@lists.freedesktop.org,
Carl Vanderlip <quic_carlv@quicinc.com>,
linux-arm-msm@vger.kernel.org,
Simona Vetter <simona.vetter@intel.com>
Subject: Re: [PATCH 4/8] accel/qaic: delete qaic_bo.handle
Date: Mon, 2 Jun 2025 16:43:35 +0200 [thread overview]
Message-ID: <aD24l3NoZWWwScx6@phenom.ffwll.local> (raw)
In-Reply-To: <70ad82b5-19f3-4e05-bc7a-858dafc563ef@oss.qualcomm.com>
On Wed, May 28, 2025 at 09:15:22AM -0600, Jeff Hugo wrote:
> On 5/28/2025 3:13 AM, Simona Vetter wrote:
> > Handles are per-file, not global, so this makes no sense. Plus it's
> > set only after calling drm_gem_handle_create(), and drivers are not
> > allowed to further intialize a bo after that function has published it
> > already.
>
> intialize -> initialize
>
> > It is also entirely unused, which helps enormously with removing it
> > :-)
>
> There is a downstream reference to it which hasn't quite made it upstream
> yet, but tweaking that should be fine. This is clearly a problem anyways, so
> we'll need to find a solution regardless. Thank you very much for the audit.
>
> > Since we're still holding a reference to the bo nothing bad can
> > happen, hence not cc: stable material.
> >
> > Cc: Jeff Hugo <jeff.hugo@oss.qualcomm.com>
> > Cc: Carl Vanderlip <quic_carlv@quicinc.com>
> > Cc: linux-arm-msm@vger.kernel.org
> > Signed-off-by: Simona Vetter <simona.vetter@ffwll.ch>
> > Signed-off-by: Simona Vetter <simona.vetter@intel.com>
>
> SOB chain seems weird to me. I got this email from @ffwll.ch, which would be
> the author. Where is @intel.com contributing to the handoff of the patch?
I work for intel, so I just whack both of my emails on there for sob
purposes. The intel email tends to be a blackhole for public mail, which
is why I don't use it as From: for anything public.
> Overall, looks good to me. Seems like either I can ack this, and you can
> merge, or I can just take it forward. I have no preference. Do you?
Whatever you like most, I'll resend the series with the wrong patches
dropped soon anyway.
-Sima
--
Simona Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
next prev parent reply other threads:[~2025-06-02 14:43 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-28 9:12 [PATCH 0/8] drm/gem: Audit around handle_create races Simona Vetter
2025-05-28 9:12 ` [PATCH 1/8] drm/gem: Fix race in drm_gem_handle_create_tail() Simona Vetter
2025-05-28 9:26 ` Simona Vetter
2025-05-28 13:20 ` Jacek Lawrynowicz
2025-06-02 15:15 ` Thomas Zimmermann
2025-06-03 11:45 ` Simona Vetter
2025-06-03 12:40 ` Thomas Zimmermann
2025-06-04 9:02 ` Simona Vetter
2025-05-28 9:13 ` [PATCH 2/8] drm/fdinfo: Switch to idr_for_each() in drm_show_memory_stats() Simona Vetter
2025-05-28 9:22 ` Simona Vetter
2025-05-28 20:10 ` kernel test robot
2025-05-28 9:13 ` [PATCH 3/8] drm/panthor: Fix UAF in panthor_gem_create_with_handle() debugfs code Simona Vetter
2025-05-29 12:31 ` kernel test robot
2025-06-01 14:06 ` Adrián Larumbe
2025-06-02 14:46 ` Simona Vetter
2025-05-28 9:13 ` [PATCH 4/8] accel/qaic: delete qaic_bo.handle Simona Vetter
2025-05-28 15:15 ` Jeff Hugo
2025-06-02 14:43 ` Simona Vetter [this message]
2025-06-03 14:43 ` Jeff Hugo
2025-06-06 16:25 ` Jeff Hugo
2025-05-28 9:13 ` [PATCH 5/8] drm/amd/kfd: Add comment about possible drm_gem_handle_create() race Simona Vetter
2025-05-28 9:13 ` [PATCH 6/8] drm/amdgpu: Add comments about drm_file.object_idr issues Simona Vetter
2025-05-28 9:22 ` Simona Vetter
2025-05-28 9:13 ` [PATCH 7/8] drm/vmwgfx: " Simona Vetter
2025-05-28 9:23 ` Simona Vetter
2025-05-28 9:13 ` [PATCH 8/8] drm/xe: " Simona Vetter
2025-05-28 9:24 ` Simona Vetter
2025-05-28 9:19 ` ✓ CI.Patch_applied: success for drm/gem: Audit around handle_create races Patchwork
2025-05-28 9:20 ` ✗ CI.checkpatch: warning " Patchwork
2025-05-28 9:21 ` ✓ CI.KUnit: success " Patchwork
2025-05-28 9:24 ` ✗ CI.Build: failure " Patchwork
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=aD24l3NoZWWwScx6@phenom.ffwll.local \
--to=simona.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jeff.hugo@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=quic_carlv@quicinc.com \
--cc=simona.vetter@intel.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 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.