From: Fedor Pchelkin <pchelkin@ispras.ru>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>, stable@vger.kernel.org
Cc: Christian Koenig <christian.koenig@amd.com>,
Matthew Brost <matthew.brost@intel.com>,
Simon Richter <Simon.Richter@hogyros.de>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
lvc-project@linuxtesting.org
Subject: Re: [PATCH 6.1] drm/ttm: fix up length check inside ttm_bo_vm_access()
Date: Fri, 16 Jan 2026 22:36:06 +0300 [thread overview]
Message-ID: <aWqS00tHXSsh_rwL@fedora> (raw)
In-Reply-To: <20260116185007.1243557-1-pchelkin@ispras.ru>
On Fri, 16. Jan 21:50, Fedor Pchelkin wrote:
> The backport of 491adc6a0f99 ("drm/ttm: Avoid NULL pointer deref for
> evicted BOs") is currently in 5.10-5.15 queues and it may be fixed up in
> place.
That's actually in queue for 5.15 only, not 5.10.
prev parent reply other threads:[~2026-01-16 19:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-16 18:50 [PATCH 6.1] drm/ttm: fix up length check inside ttm_bo_vm_access() Fedor Pchelkin
2026-01-16 19:36 ` Fedor Pchelkin [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=aWqS00tHXSsh_rwL@fedora \
--to=pchelkin@ispras.ru \
--cc=Simon.Richter@hogyros.de \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lvc-project@linuxtesting.org \
--cc=matthew.brost@intel.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