From: Nirmoy Das <nirmoy.das@linux.intel.com>
To: Jiasheng Jiang <jiashengjiangcool@outlook.com>,
jani.nikula@linux.intel.com, joonas.lahtinen@linux.intel.com,
rodrigo.vivi@intel.com, tursulin@ursulin.net, airlied@gmail.com,
daniel@ffwll.ch, chris@chris-wilson.co.uk
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/i915: Correct error handler
Date: Mon, 13 May 2024 09:25:45 +0200 [thread overview]
Message-ID: <ce1e1097-2e7d-475b-ac17-3b84aec473e2@linux.intel.com> (raw)
In-Reply-To: <BYAPR03MB41680146FAD88A8F26C3827BADE02@BYAPR03MB4168.namprd03.prod.outlook.com>
On 5/11/2024 5:48 PM, Jiasheng Jiang wrote:
> Replace "slab_priorities" with "slab_dependencies" in the error handler to avoid memory leak.
Nice catch. I would make the subject more like:
drm/i915: Fix memory leak by correcting cache object name in error handler
>
> Fixes: 32eb6bcfdda9 ("drm/i915: Make request allocation caches global")
Also need Cc: <stable@vger.kernel.org> # v5.2+
With those:
Reviewed-by: Nirmoy Das <nirmoy.das@intel.com>
Nirmoy
> Signed-off-by: Jiasheng Jiang <jiashengjiangcool@outlook.com>
> ---
> drivers/gpu/drm/i915/i915_scheduler.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_scheduler.c b/drivers/gpu/drm/i915/i915_scheduler.c
> index 762127dd56c5..70a854557e6e 100644
> --- a/drivers/gpu/drm/i915/i915_scheduler.c
> +++ b/drivers/gpu/drm/i915/i915_scheduler.c
> @@ -506,6 +506,6 @@ int __init i915_scheduler_module_init(void)
> return 0;
>
> err_priorities:
> - kmem_cache_destroy(slab_priorities);
> + kmem_cache_destroy(slab_dependencies);
> return -ENOMEM;
> }
next prev parent reply other threads:[~2024-05-13 7:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-11 15:48 [PATCH] drm/i915: Correct error handler Jiasheng Jiang
2024-05-13 7:25 ` Nirmoy Das [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-05-13 14:23 Jiasheng Jiang
2024-05-13 14:14 Jiasheng Jiang
2024-05-11 15:39 Jiasheng Jiang
2024-05-10 19:40 Jiasheng Jiang
2024-05-11 15:36 ` Jiasheng Jiang
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=ce1e1097-2e7d-475b-ac17-3b84aec473e2@linux.intel.com \
--to=nirmoy.das@linux.intel.com \
--cc=airlied@gmail.com \
--cc=chris@chris-wilson.co.uk \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=jiashengjiangcool@outlook.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rodrigo.vivi@intel.com \
--cc=tursulin@ursulin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox