From: Matthew Auld <matthew.auld@intel.com>
To: Arunpravin <Arunpravin.PaneerSelvam@amd.com>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
amd-gfx@lists.freedesktop.org
Cc: alexander.deucher@amd.com, christian.koenig@amd.com
Subject: Re: [Intel-gfx] [PATCH] drm: Fix a infinite loop condition when order becomes 0
Date: Tue, 15 Mar 2022 11:31:10 +0000 [thread overview]
Message-ID: <01c75d44-80b1-3368-e568-0e38072138d6@intel.com> (raw)
In-Reply-To: <20220314194049.534471-1-Arunpravin.PaneerSelvam@amd.com>
On 14/03/2022 19:40, Arunpravin wrote:
> handle a situation in the condition order-- == min_order,
> when order = 0, leading to order = -1, it now won't exit
> the loop. To avoid this problem, added a order check in
> the same condition, (i.e) when order is 0, we return
> -ENOSPC
>
> Signed-off-by: Arunpravin <Arunpravin.PaneerSelvam@amd.com>
Hmm, it sounded like we were instead going to go with the round_up(size,
min_page_size), or check and bail if the size is misaligned, in which
case we don't need this, AFAICT.
> ---
> drivers/gpu/drm/drm_buddy.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/drm_buddy.c b/drivers/gpu/drm/drm_buddy.c
> index 72f52f293249..5ab66aaf2bbd 100644
> --- a/drivers/gpu/drm/drm_buddy.c
> +++ b/drivers/gpu/drm/drm_buddy.c
> @@ -685,7 +685,7 @@ int drm_buddy_alloc_blocks(struct drm_buddy *mm,
> if (!IS_ERR(block))
> break;
>
> - if (order-- == min_order) {
> + if (!order || order-- == min_order) {
> err = -ENOSPC;
> goto err_free;
> }
prev parent reply other threads:[~2022-03-15 11:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-14 19:40 [Intel-gfx] [PATCH] drm: Fix a infinite loop condition when order becomes 0 Arunpravin
2022-03-15 1:11 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2022-03-15 5:36 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-03-15 8:19 ` [Intel-gfx] [PATCH] " Paul Menzel
2022-03-15 9:01 ` Arunpravin
2022-03-15 9:05 ` Paul Menzel
2022-03-15 15:42 ` Arunpravin
2022-03-15 15:44 ` Paul Menzel
2022-03-16 6:49 ` Arunpravin Paneer Selvam
2022-03-16 6:58 ` Paul Menzel
2022-03-21 6:15 ` Arunpravin Paneer Selvam
2022-03-15 11:31 ` Matthew Auld [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=01c75d44-80b1-3368-e568-0e38072138d6@intel.com \
--to=matthew.auld@intel.com \
--cc=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 \
/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