From: sashiko-bot@kernel.org
To: yaolu@kylinos.cn
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/gem: Fix resource leaks in drm_gem_huge_mnt_create() error paths
Date: Tue, 09 Jun 2026 02:37:54 +0000 [thread overview]
Message-ID: <20260609023754.F31E41F00893@smtp.kernel.org> (raw)
In-Reply-To: <20260609022504.65722-1-yaolu@kylinos.cn>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
Pre-existing issues:
- [Critical] drm_gem_huge_mnt_create() leaves an ERR_PTR or a freed pointer in dev->huge_mnt on failure, leading to cascading failures or Use-After-Free during GEM object creation.
--
commit 7e7660e13d434072f394d83fe8c601ac0c32b376
Author: Lu Yao <yaolu@kylinos.cn>
drm/gem: Fix resource leaks in drm_gem_huge_mnt_create() error paths
This commit fixes two resource leaks in the error handling paths of
drm_gem_huge_mnt_create() by releasing the filesystem type reference and
the fs_context allocated for the mount.
> diff --git a/drivers/gpu/drm/drm_gem.c b/drivers/gpu/drm/drm_gem.c
> index e3ed684ddcf29..6f0751d668ad9 100644
> --- a/drivers/gpu/drm/drm_gem.c
> +++ b/drivers/gpu/drm/drm_gem.c
[ ... ]
> @@ -122,19 +122,24 @@ int drm_gem_huge_mnt_create(struct drm_device *dev, const char *value)
[ ... ]
> ret = vfs_parse_fs_string(fc, "huge", value);
> if (unlikely(ret))
> - return -ENOPARAM;
> + goto err;
>
> dev->huge_mnt = fc_mount_longterm(fc);
> put_fs_context(fc);
>
> return drmm_add_action_or_reset(dev, drm_gem_huge_mnt_free, NULL);
[Severity: Critical]
This is a pre-existing issue, but does this leave an invalid pointer in
dev->huge_mnt on failure?
If fc_mount_longterm() fails and returns an ERR_PTR, it gets unconditionally
assigned to dev->huge_mnt. If drmm_add_action_or_reset() then succeeds,
drm_gem_get_huge_mnt() will later return this ERR_PTR. This bypasses the NULL
check in drm_gem_object_init() and causes shmem_file_setup_with_mnt() to fail
for subsequent allocations.
Additionally, if drmm_add_action_or_reset() fails, it triggers its cleanup
action drm_gem_huge_mnt_free(), which calls kern_unmount(dev->huge_mnt).
However, dev->huge_mnt is not reset to NULL. Later, drm_gem_object_init()
could pass this freed pointer to shmem_file_setup_with_mnt(), resulting in
a use-after-free.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260609022504.65722-1-yaolu@kylinos.cn?part=1
prev parent reply other threads:[~2026-06-09 2:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-09 2:25 [PATCH] drm/gem: Fix resource leaks in drm_gem_huge_mnt_create() error paths yaolu
2026-06-09 2:37 ` sashiko-bot [this message]
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=20260609023754.F31E41F00893@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=yaolu@kylinos.cn \
/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