public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Ramalingam C <ramalingam.c@intel.com>
To: Bommu Krishnaiah <krishnaiah.bommu@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 0/4] The Following Patches are to Fix the Critical KclockWork Errors in i915_gem and gt
Date: Tue, 29 Jun 2021 13:44:42 +0530	[thread overview]
Message-ID: <20210629081442.GA29108@intel.com> (raw)
In-Reply-To: <20210628143829.22995-1-krishnaiah.bommu@intel.com>

each patch's commit message is empty except for signed-off and cc.
Please provide corresponding KclockWork Errors that is getting fixed.

Ram.

On 2021-06-28 at 20:08:25 +0530, Bommu Krishnaiah wrote:
> Klock work Fix for NULL dereferencing in i915_gem_ttm.c
> original issue statement "Pointer 'sg' returned from call to function '__i915_gem_object_get_sg' at line 592 may be NULL and will be dereferenced at line 594."
> 
> Klock work Fix for NULL dereferencing in i915_gem_mman.c
> original issue statement "Null pointer 'mmo' that comes from line 892 may be dereferenced at line 964."
> 
> Klock work Fix for possible memory leak in intel_execlists_submission.c
> original issue statement “Possible memory leak. Dynamic memory stored in 've' allocated through function 'kzalloc' at line 3721 can be lost at line 3850”
> 
> Klock work Fix for uninitialized array intel_migrate.c
> original issue statement "'engines' array elements might be used uninitialized in this function."
> 
> Bommu Krishnaiah (4):
>   Klock work Fix for NULL dereferencing in i915_gem_ttm.c
>   Klock work Fix for NULL dereferencing in i915_gem_mman.c
>   Klock work Fix for possible memory leak in
>     intel_execlists_submission.c
>   Klock work Fix for uninitialized array intel_migrate.c
> 
>  drivers/gpu/drm/i915/gem/i915_gem_mman.c             | 2 ++
>  drivers/gpu/drm/i915/gem/i915_gem_ttm.c              | 1 +
>  drivers/gpu/drm/i915/gt/intel_execlists_submission.c | 1 +
>  drivers/gpu/drm/i915/gt/intel_migrate.c              | 4 ++++
>  4 files changed, 8 insertions(+)
> 
> -- 
> 2.25.1
> 
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

      parent reply	other threads:[~2021-06-29  8:13 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-28 14:38 [Intel-gfx] [PATCH 0/4] The Following Patches are to Fix the Critical KclockWork Errors in i915_gem and gt Bommu Krishnaiah
2021-06-28 14:38 ` [Intel-gfx] [PATCH 1/4] Klock work Fix for NULL dereferencing in i915_gem_ttm.c Bommu Krishnaiah
2021-06-29  9:26   ` Ramalingam C
2021-07-01  9:39   ` Matthew Auld
2021-07-01  9:49     ` Matthew Auld
2021-06-28 14:38 ` [Intel-gfx] [PATCH 2/4] Klock work Fix for NULL dereferencing in i915_gem_mman.c Bommu Krishnaiah
2021-06-29  9:23   ` Ramalingam C
2021-06-28 14:38 ` [Intel-gfx] [PATCH 3/4] Klock work Fix for possible memory leak in intel_execlists_submission.c Bommu Krishnaiah
2021-06-28 15:01   ` Tvrtko Ursulin
2021-06-28 14:38 ` [Intel-gfx] [PATCH 4/4] Klock work Fix for uninitialized array intel_migrate.c Bommu Krishnaiah
2021-06-29  8:52   ` Ramalingam C
2021-06-28 18:37 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for The Following Patches are to Fix the Critical KclockWork Errors in i915_gem and gt Patchwork
2021-06-28 18:37 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2021-06-28 19:07 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-06-28 22:46 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2021-06-29  8:14 ` Ramalingam C [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=20210629081442.GA29108@intel.com \
    --to=ramalingam.c@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=krishnaiah.bommu@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox