From: Arunpravin Paneer Selvam <arunpravin.paneerselvam@amd.com>
To: "Christian König" <christian.koenig@amd.com>,
"Matthew Auld" <matthew.auld@intel.com>,
dri-devel@lists.freedesktop.org, amd-gfx@lists.freedesktop.org,
intel-gfx@lists.freedesktop.org
Cc: alexander.deucher@amd.com, mario.limonciello@amd.com,
spasswolf@web.de, stable@vger.kernel.org
Subject: Re: [PATCH] drm/buddy: Modify duplicate list_splice_tail call
Date: Mon, 19 Feb 2024 10:25:04 +0530 [thread overview]
Message-ID: <dbc0f30e-2f5d-683c-116f-78aad68f5a29@amd.com> (raw)
In-Reply-To: <fc77efca-137c-4d39-b74a-6a3e1ca39987@amd.com>
Hi Christian,
On 2/16/2024 5:29 PM, Christian König wrote:
>
>
> Am 16.02.24 um 12:46 schrieb Arunpravin Paneer Selvam:
>>
>>
>> On 2/16/2024 4:41 PM, Matthew Auld wrote:
>>> On 16/02/2024 10:00, Arunpravin Paneer Selvam wrote:
>>>> Remove the duplicate list_splice_tail call when the
>>>> total_allocated < size condition is true.
>>>>
>>>> Cc: <stable@vger.kernel.org> # 6.7+
>>>> Fixes: 8746c6c9dfa3 ("drm/buddy: Fix alloc_range() error handling
>>>> code")
>>>> Reported-by: Bert Karwatzki <spasswolf@web.de>
>>>> Signed-off-by: Arunpravin Paneer Selvam
>>>> <Arunpravin.PaneerSelvam@amd.com>
>>>> ---
>>>> drivers/gpu/drm/drm_buddy.c | 4 ++--
>>>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>>>
>>>> diff --git a/drivers/gpu/drm/drm_buddy.c b/drivers/gpu/drm/drm_buddy.c
>>>> index c1a99bf4dffd..c4222b886db7 100644
>>>> --- a/drivers/gpu/drm/drm_buddy.c
>>>> +++ b/drivers/gpu/drm/drm_buddy.c
>>>> @@ -538,13 +538,13 @@ static int __alloc_range(struct drm_buddy *mm,
>>>> list_add(&block->left->tmp_link, dfs);
>>>> } while (1);
>>>> - list_splice_tail(&allocated, blocks);
>>>> -
>>>> if (total_allocated < size) {
>>>> err = -ENOSPC;
>>>> goto err_free;
>>>> }
>>>> + list_splice_tail(&allocated, blocks);
>>>
>>> Sigh. Can we extend the unit test(s) to catch this?
>> Sure, Let me check.
>
> In the meantime I'm going to push this one to drm-misc-fixes.
Thank you!
>
> Regards,
> Christian.
>
>>
>> Regards,
>> Arun.
>>>
>>> Reviewed-by: Matthew Auld <matthew.auld@intel.com>
>>>
>>>> +
>>>> return 0;
>>>> err_undo:
>>>>
>>>> base-commit: a64056bb5a3215bd31c8ce17d609ba0f4d5c55ea
>>
>
next prev parent reply other threads:[~2024-02-19 4:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-16 10:00 [PATCH] drm/buddy: Modify duplicate list_splice_tail call Arunpravin Paneer Selvam
2024-02-16 11:11 ` Matthew Auld
2024-02-16 11:46 ` Arunpravin Paneer Selvam
2024-02-16 11:59 ` Christian König
2024-02-19 4:55 ` Arunpravin Paneer Selvam [this message]
2024-02-16 21:08 ` ✗ Fi.CI.SPARSE: warning for " Patchwork
2024-02-16 21:23 ` ✓ Fi.CI.BAT: success " Patchwork
2024-02-17 13:07 ` ✗ Fi.CI.IGT: failure " 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=dbc0f30e-2f5d-683c-116f-78aad68f5a29@amd.com \
--to=arunpravin.paneerselvam@amd.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=mario.limonciello@amd.com \
--cc=matthew.auld@intel.com \
--cc=spasswolf@web.de \
--cc=stable@vger.kernel.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