From: Shuicheng Lin <shuicheng.lin@intel.com>
To: dri-devel@lists.freedesktop.org
Cc: "Shuicheng Lin" <shuicheng.lin@intel.com>,
intel-xe@lists.freedesktop.org,
"Natalie Vock" <nat@pixelcluster.dev>,
"Arun Pravin" <arunpravin.paneerselvam@amd.com>,
"Matthew Auld" <matthew.auld@intel.com>,
"Matthew Brost" <matthew.brost@intel.com>,
"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
linux-kernel@vger.kernel.org
Subject: [PATCH v2] drm/ttm: Don't warn on oversized page directory allocations
Date: Sat, 21 Nov 2026 01:57:00 -0800 [thread overview]
Message-ID: <20261121095703.1571697-2-shuicheng.lin@intel.com> (raw)
The page directory size in ttm_tt_alloc_page_directory() and
ttm_dma_tt_alloc_page_directory() comes from the user-supplied BO size.
kvmalloc() warns on requests above INT_MAX unless __GFP_NOWARN is set,
so userspace can trigger a WARN (or a panic with panic_on_warn) by
creating a huge BO, e.g. a 1 TiB sysmem BO on xe with DEFER_BACKING:
WARNING: mm/slub.c:7144 at __kvmalloc_node_noprof+0x665/0x810
Call Trace:
ttm_tt_init+0x1e0/0x2b0
xe_ttm_tt_create+0x2cf/0x4b0 [xe]
ttm_tt_create+0x17c/0x310
...
xe_gem_create_ioctl+0x70f/0x12b0 [xe]
The failure is already handled and the ioctl returns -ENOMEM, so pass
__GFP_NOWARN to both allocations.
v2 (Sashiko):
- Also pass __GFP_NOWARN in ttm_sg_tt_alloc_page_directory(), whose
size comes from an imported dma-buf
Fixes: 7661809d493b ("mm: don't allow oversized kvmalloc() calls")
Signed-off-by: Shuicheng Lin <shuicheng.lin@intel.com>
---
drivers/gpu/drm/ttm/ttm_tt.c | 9 ++++++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/drivers/gpu/drm/ttm/ttm_tt.c b/drivers/gpu/drm/ttm/ttm_tt.c
index b645a1818184..7d6c9247507b 100644
--- a/drivers/gpu/drm/ttm/ttm_tt.c
+++ b/drivers/gpu/drm/ttm/ttm_tt.c
@@ -117,7 +117,8 @@ EXPORT_SYMBOL_FOR_TESTS_ONLY(ttm_tt_create);
*/
static int ttm_tt_alloc_page_directory(struct ttm_tt *ttm)
{
- ttm->pages = kvcalloc(ttm->num_pages, sizeof(void*), GFP_KERNEL);
+ ttm->pages = kvcalloc(ttm->num_pages, sizeof(void *),
+ GFP_KERNEL | __GFP_NOWARN);
if (!ttm->pages)
return -ENOMEM;
@@ -127,7 +128,8 @@ static int ttm_tt_alloc_page_directory(struct ttm_tt *ttm)
static int ttm_dma_tt_alloc_page_directory(struct ttm_tt *ttm)
{
ttm->pages = kvcalloc(ttm->num_pages, sizeof(*ttm->pages) +
- sizeof(*ttm->dma_address), GFP_KERNEL);
+ sizeof(*ttm->dma_address),
+ GFP_KERNEL | __GFP_NOWARN);
if (!ttm->pages)
return -ENOMEM;
@@ -137,7 +139,8 @@ static int ttm_dma_tt_alloc_page_directory(struct ttm_tt *ttm)
static int ttm_sg_tt_alloc_page_directory(struct ttm_tt *ttm)
{
- ttm->dma_address = kvzalloc_objs(*ttm->dma_address, ttm->num_pages);
+ ttm->dma_address = kvzalloc_objs(*ttm->dma_address, ttm->num_pages,
+ GFP_KERNEL | __GFP_NOWARN);
if (!ttm->dma_address)
return -ENOMEM;
base-commit: 61df0d1929e7e99d38404a1be02c461a8f6a3f5a
--
2.43.0
reply other threads:[~2026-11-21 9:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20261121095703.1571697-2-shuicheng.lin@intel.com \
--to=shuicheng.lin@intel.com \
--cc=arunpravin.paneerselvam@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=matthew.auld@intel.com \
--cc=matthew.brost@intel.com \
--cc=mripard@kernel.org \
--cc=nat@pixelcluster.dev \
--cc=thomas.hellstrom@linux.intel.com \
--cc=tzimmermann@suse.de \
/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
all inboxes | Powered by JetHome®