Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Shyti <andi.shyti@linux.intel.com>
To: Ashutosh Dixit <ashutosh.dixit@intel.com>
Cc: intel-gfx@lists.freedesktop.org, Andrzej Hajda <andrzej.hajda@intel.com>
Subject: Re: [Intel-gfx] [PATCH] drm/i915/gt: Fix memory leaks in per-gt sysfs
Date: Tue, 10 May 2022 07:47:57 +0200	[thread overview]
Message-ID: <Ynn8jWcli0jOoIWV@intel.intel> (raw)
In-Reply-To: <20220427203833.44449-1-ashutosh.dixit@intel.com>

Hi Ashutosh,

On Wed, Apr 27, 2022 at 01:38:33PM -0700, Ashutosh Dixit wrote:
> All kmalloc'd kobjects need a kobject_put() to free memory. For example in
> previous code, kobj_gt_release() never gets called. The requirement of
> kobject_put() now results in a slightly different code organization.
> 
> v2: s/gtn/gt/ (Andi)
> 
> Cc: Andi Shyti <andi.shyti@intel.com>
> Cc: Andrzej Hajda <andrzej.hajda@intel.com>
> Fixes: b770bcfae9ad ("drm/i915/gt: create per-tile sysfs interface")
> Signed-off-by: Ashutosh Dixit <ashutosh.dixit@intel.com>

I'm still not convinced this patch is 100% correct, but I think
it's better thank what it was and it's not addressing Andrzej's
comment.

As of now, though, I'm not able to think of a better way of doing
it and if Andrzej doesn't have a better solution I would just
tag it:

Reviewed-by: Andi Shyti <andi.shyti@linux.intel.com>

As soon as I will have some time I will test it to proof
Andrzej's concern.

Thanks for taking care of this,
Andi

      parent reply	other threads:[~2022-05-10  5:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-27 20:38 [Intel-gfx] [PATCH] drm/i915/gt: Fix memory leaks in per-gt sysfs Ashutosh Dixit
2022-04-27 20:53 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for " Patchwork
2022-04-27 21:23 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-04-27 22:45 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-04-28  0:41   ` Dixit, Ashutosh
2022-04-28 15:42     ` Vudum, Lakshminarayana
2022-04-28 15:33 ` [Intel-gfx] ✓ Fi.CI.IGT: success " Patchwork
2022-05-10  5:47 ` Andi Shyti [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=Ynn8jWcli0jOoIWV@intel.intel \
    --to=andi.shyti@linux.intel.com \
    --cc=andrzej.hajda@intel.com \
    --cc=ashutosh.dixit@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    /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