From: Triet Hoang <triet.hoang.dev@gmail.com>
To: sidong.yang@furiosa.ai, royalnet026@gmail.com
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
ogabbay@kernel.org, tomeu@tomeuvizoso.net,
triet.hoang.dev@gmail.com
Subject: [PATCH v6 0/2] accel/rocket: Fix allocation handling and scheduler array leak
Date: Mon, 14 Sep 2026 11:56:03 +0700 [thread overview]
Message-ID: <20260914045605.381933-1-triet.hoang.dev@gmail.com> (raw)
This small series addresses allocation and memory management issues in
the accel/rocket driver:
1. Patch 1 ensures proper allocation checks before using pointers
in rocket_job_open()
2. Patch 2 fixes an unreachable memory leak of the scheduler array when
running on single-core setups (e.g., num_cores == 1), where
drm_sched_entity_init() drops the array pointer.
Link to v5: https://lore.kernel.org/all/20260818041505.1579320-1-triet.hoang.dev@gmail.com/
Changes in v6:
- Rebase on top of drm-misc-next (base commit 5052ea2e6bfc43c64b851c596d3675d17e05e631)
- Addressed review feedback from previous iterations.
- Added Fixes and Tested-by tags where applicable.
Triet Hoang (2):
drm/rocket: Check allocations before use
drm/rocket: Keep scheduler allocation in rocket_file_priv
drivers/accel/rocket/rocket_drv.h | 1 +
drivers/accel/rocket/rocket_job.c | 13 +++++++++----
2 files changed, 10 insertions(+), 4 deletions(-)
--
2.53.0
next reply other threads:[~2026-09-14 4:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-14 4:56 Triet Hoang [this message]
2026-09-14 4:56 ` [PATCH v6 1/2] accel/rocket: Check allocations before use Triet Hoang
2026-09-14 5:08 ` sashiko-bot
2026-09-14 13:34 ` Igor Paunovic
2026-09-14 4:56 ` [PATCH v6 2/2] drm/rocket: Keep scheduler allocation in rocket_file_priv Triet Hoang
2026-09-14 5:09 ` sashiko-bot
2026-09-14 13:30 ` Igor Paunovic
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=20260914045605.381933-1-triet.hoang.dev@gmail.com \
--to=triet.hoang.dev@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ogabbay@kernel.org \
--cc=royalnet026@gmail.com \
--cc=sidong.yang@furiosa.ai \
--cc=tomeu@tomeuvizoso.net \
/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.