From: Greg KH <gregkh@linuxfoundation.org>
To: Yunxiang Li <Yunxiang.Li@amd.com>
Cc: stable@vger.kernel.org, "Christian König" <christian.koenig@amd.com>
Subject: Re: [PATCH 6.4.y] drm/ttm: fix bulk_move corruption when adding a entry
Date: Mon, 24 Jul 2023 08:29:19 +0200 [thread overview]
Message-ID: <2023072420-dangle-liftoff-c1ce@gregkh> (raw)
In-Reply-To: <20230724004330.1320-1-Yunxiang.Li@amd.com>
On Sun, Jul 23, 2023 at 08:43:26PM -0400, Yunxiang Li wrote:
> When the resource is the first in the bulk_move range, adding it again
> (thus moving it to the tail) will corrupt the list since the first
> pointer is not moved. This eventually lead to null pointer deref in
> ttm_lru_bulk_move_del()
>
> Fixes: fee2ede15542 ("drm/ttm: rework bulk move handling v5")
> Signed-off-by: Yunxiang Li <Yunxiang.Li@amd.com>
> Reviewed-by: Christian König <christian.koenig@amd.com>
> CC: stable@vger.kernel.org
> Link: https://patchwork.freedesktop.org/patch/msgid/20230622141902.28718-3-Yunxiang.Li@amd.com
> Signed-off-by: Christian König <christian.koenig@amd.com>
> (cherry picked from commit 4481913607e58196c48a4fef5e6f45350684ec3c)
> ---
> drivers/gpu/drm/ttm/ttm_resource.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
Both now queued up, thanks.
greg k-h
next prev parent reply other threads:[~2023-07-24 6:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-21 12:20 FAILED: patch "[PATCH] drm/ttm: fix bulk_move corruption when adding a entry" failed to apply to 6.4-stable tree gregkh
2023-07-21 12:51 ` Li, Yunxiang (Teddy)
2023-07-21 13:27 ` gregkh
2023-07-21 20:01 ` Li, Yunxiang (Teddy)
2023-07-22 11:48 ` gregkh
2023-07-24 0:43 ` [PATCH 6.4.y] drm/ttm: fix bulk_move corruption when adding a entry Yunxiang Li
2023-07-24 6:29 ` Greg KH [this message]
2023-07-24 0:44 ` [PATCH 6.1.y] " Yunxiang Li
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=2023072420-dangle-liftoff-c1ce@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=Yunxiang.Li@amd.com \
--cc=christian.koenig@amd.com \
--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