From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Mirsad Goran Todorovac <mirsad.todorovac@alu.unizg.hr>,
srinivas pandruvada <srinivas.pandruvada@linux.intel.com>,
LKML <linux-kernel@vger.kernel.org>,
jani.nikula@linux.intel.com, joonas.lahtinen@linux.intel.com,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: intel-gfx@lists.freedesktop.org,
Thorsten Leemhuis <regressions@leemhuis.info>
Subject: Re: [Intel-gfx] LOOKS GOOD: Possible regression in drm/i915 driver: memleak
Date: Mon, 9 Jan 2023 15:00:49 +0000 [thread overview]
Message-ID: <9c86dff0-e7f4-60b9-ed3e-6ad51cacaa01@linux.intel.com> (raw)
In-Reply-To: <edab9da6-df81-7167-acdd-f2ea22c7ed90@alu.unizg.hr>
On 25/12/2022 22:48, Mirsad Goran Todorovac wrote:
> On 22. 12. 2022. 09:04, Tvrtko Ursulin wrote:
>>
>> In the meantime definitely thanks a lot for testing this quickly and
>> reporting back!
>
> Don't think much of it - anyone with CONFIG_KMEMLEAK enabled could have
> caught this bug.
>
> I was surprised that you found the fix in less than an hour without me
> having to bisect :)
Fix sadly has a problem handling shared buffers so different version
will hopefully appear soon.
Regards,
Tvrtko
WARNING: multiple messages have this Message-ID (diff)
From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Mirsad Goran Todorovac <mirsad.todorovac@alu.unizg.hr>,
srinivas pandruvada <srinivas.pandruvada@linux.intel.com>,
LKML <linux-kernel@vger.kernel.org>,
jani.nikula@linux.intel.com, joonas.lahtinen@linux.intel.com,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: Thorsten Leemhuis <regressions@leemhuis.info>,
intel-gfx@lists.freedesktop.org
Subject: Re: LOOKS GOOD: Possible regression in drm/i915 driver: memleak
Date: Mon, 9 Jan 2023 15:00:49 +0000 [thread overview]
Message-ID: <9c86dff0-e7f4-60b9-ed3e-6ad51cacaa01@linux.intel.com> (raw)
In-Reply-To: <edab9da6-df81-7167-acdd-f2ea22c7ed90@alu.unizg.hr>
On 25/12/2022 22:48, Mirsad Goran Todorovac wrote:
> On 22. 12. 2022. 09:04, Tvrtko Ursulin wrote:
>>
>> In the meantime definitely thanks a lot for testing this quickly and
>> reporting back!
>
> Don't think much of it - anyone with CONFIG_KMEMLEAK enabled could have
> caught this bug.
>
> I was surprised that you found the fix in less than an hour without me
> having to bisect :)
Fix sadly has a problem handling shared buffers so different version
will hopefully appear soon.
Regards,
Tvrtko
next prev parent reply other threads:[~2023-01-09 15:01 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-20 14:33 Possible regression in drm/i915 driver: memleak Mirsad Todorovac
2022-12-20 15:22 ` [Intel-gfx] " srinivas pandruvada
2022-12-20 15:22 ` srinivas pandruvada
2022-12-20 15:52 ` [Intel-gfx] " Tvrtko Ursulin
2022-12-20 15:52 ` Tvrtko Ursulin
2022-12-20 17:20 ` [Intel-gfx] " Mirsad Goran Todorovac
2022-12-20 17:20 ` Mirsad Goran Todorovac
2022-12-20 19:34 ` [Intel-gfx] LOOKS GOOD: " Mirsad Todorovac
2022-12-20 19:34 ` Mirsad Todorovac
2022-12-21 7:15 ` [Intel-gfx] " Mirsad Goran Todorovac
2022-12-21 7:15 ` Mirsad Goran Todorovac
2022-12-22 0:12 ` [Intel-gfx] LOOKS GOOD: " Mirsad Goran Todorovac
2022-12-22 0:12 ` Mirsad Goran Todorovac
2022-12-22 8:04 ` [Intel-gfx] " Tvrtko Ursulin
2022-12-22 8:04 ` Tvrtko Ursulin
2022-12-22 15:21 ` [Intel-gfx] " Mirsad Goran Todorovac
2022-12-22 15:21 ` Mirsad Goran Todorovac
2022-12-23 12:18 ` [Intel-gfx] " Tvrtko Ursulin
2022-12-23 12:18 ` Tvrtko Ursulin
2022-12-25 21:11 ` [Intel-gfx] " Mirsad Goran Todorovac
2022-12-25 21:11 ` Mirsad Goran Todorovac
2022-12-25 22:48 ` [Intel-gfx] " Mirsad Goran Todorovac
2022-12-25 22:48 ` Mirsad Goran Todorovac
2023-01-09 15:00 ` Tvrtko Ursulin [this message]
2023-01-09 15:00 ` Tvrtko Ursulin
2023-01-16 6:25 ` [Intel-gfx] " Mirsad Todorovac
2023-01-16 6:25 ` Mirsad Todorovac
2022-12-21 23:34 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for " Patchwork
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=9c86dff0-e7f4-60b9-ed3e-6ad51cacaa01@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mirsad.todorovac@alu.unizg.hr \
--cc=regressions@leemhuis.info \
--cc=rodrigo.vivi@intel.com \
--cc=srinivas.pandruvada@linux.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 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.