From: Mario Limonciello <mario.limonciello@amd.com>
To: "Arunpravin Paneer Selvam" <arunpravin.paneerselvam@amd.com>,
"Christian König" <christian.koenig@amd.com>,
dri-devel@lists.freedesktop.org, amd-gfx@lists.freedesktop.org,
intel-gfx@lists.freedesktop.org
Cc: alexander.deucher@amd.com, matthew.auld@intel.com
Subject: Re: [PATCH] drm/buddy: Fix alloc_range() error handling code
Date: Thu, 8 Feb 2024 07:59:06 -0600 [thread overview]
Message-ID: <21166026-22ea-4bc3-b1e0-d8896f5820ad@amd.com> (raw)
In-Reply-To: <86b5d704-9e0d-b989-1469-665e41d9b342@amd.com>
On 2/8/2024 06:06, Arunpravin Paneer Selvam wrote:
> Hi Christian,
>
> On 2/8/2024 12:27 PM, Christian König wrote:
>> Am 07.02.24 um 18:44 schrieb Arunpravin Paneer Selvam:
>>> Few users have observed display corruption when they boot
>>> the machine to KDE Plasma or playing games. We have root
>>> caused the problem that whenever alloc_range() couldn't
>>> find the required memory blocks the function was returning
>>> SUCCESS in some of the corner cases.
>>>
>>> The right approach would be if the total allocated size
>>> is less than the required size, the function should
>>> return -ENOSPC.
>>>
>>> Gitlab ticket link -
>>> https://gitlab.freedesktop.org/drm/amd/-/issues/3097
Syntax should be "Closes: $URL"
>>> Fixes: 0a1844bf0b53 ("drm/buddy: Improve contiguous memory allocation")
>>> Signed-off-by: Arunpravin Paneer Selvam
>>> <Arunpravin.PaneerSelvam@amd.com>
>>> Tested-by: Mario Limonciello <mario.limonciello@amd.com>
>>
>> Acked-by: Christian König <christian.koenig@amd.com>
>>
>> CC: stable.. ?
> I will check and add the stable kernel version.
Should be 6.7.
>
> Thanks,
> Arun.
>>
>>> ---
>>> drivers/gpu/drm/drm_buddy.c | 6 ++++++
>>> 1 file changed, 6 insertions(+)
>>>
>>> diff --git a/drivers/gpu/drm/drm_buddy.c b/drivers/gpu/drm/drm_buddy.c
>>> index f57e6d74fb0e..c1a99bf4dffd 100644
>>> --- a/drivers/gpu/drm/drm_buddy.c
>>> +++ b/drivers/gpu/drm/drm_buddy.c
>>> @@ -539,6 +539,12 @@ static int __alloc_range(struct drm_buddy *mm,
>>> } while (1);
>>> list_splice_tail(&allocated, blocks);
>>> +
>>> + if (total_allocated < size) {
>>> + err = -ENOSPC;
>>> + goto err_free;
>>> + }
>>> +
>>> return 0;
>>> err_undo:
>>
>
next prev parent reply other threads:[~2024-02-08 13:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-07 17:44 [PATCH] drm/buddy: Fix alloc_range() error handling code Arunpravin Paneer Selvam
2024-02-07 18:46 ` ✓ Fi.CI.BAT: success for " Patchwork
2024-02-07 21:09 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-02-08 6:57 ` [PATCH] " Christian König
2024-02-08 12:06 ` Arunpravin Paneer Selvam
2024-02-08 13:59 ` Mario Limonciello [this message]
2024-02-08 13:30 ` Matthew Auld
2024-02-08 13:47 ` Arunpravin Paneer Selvam
2024-02-08 14:17 ` Matthew Auld
2024-02-08 14:44 ` Matthew Auld
2024-02-09 12:58 ` Arunpravin Paneer Selvam
-- strict thread matches above, loose matches on Subject: below --
2024-02-09 15:18 Arunpravin Paneer Selvam
2024-02-09 15:26 Arunpravin Paneer Selvam
2024-02-09 18:04 ` Daniel Vetter
2024-02-09 18:36 ` Arunpravin Paneer Selvam
2024-02-09 19:40 ` Daniel Vetter
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=21166026-22ea-4bc3-b1e0-d8896f5820ad@amd.com \
--to=mario.limonciello@amd.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=arunpravin.paneerselvam@amd.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.auld@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