public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Koen Koning <koen.koning@linux.intel.com>
To: dri-devel@lists.freedesktop.org
Cc: intel-xe@lists.freedesktop.org,
	Joel Fernandes <joelagnelf@nvidia.com>,
	Matthew Auld <matthew.auld@intel.com>,
	Danilo Krummrich <dakr@kernel.org>,
	Koen Koning <koen.koning@linux.intel.com>,
	Dave Airlie <airlied@redhat.com>,
	Peter Senna Tschudin <peter.senna@linux.intel.com>,
	stable@vger.kernel.org
Subject: [PATCH v3 1/3] gpu/buddy: fix module_init() usage
Date: Thu, 19 Feb 2026 22:38:56 +0100	[thread overview]
Message-ID: <20260219213858.370675-2-koen.koning@linux.intel.com> (raw)
In-Reply-To: <20260219213858.370675-1-koen.koning@linux.intel.com>

Use subsys_initcall() instead of module_init() (which compiles to
device_initcall() for built-ins) for buddy, so its initialization code
always runs before any (built-in) drivers.
This happened to work correctly so far due to the order of linking in
the Makefiles, but this should not be relied upon.

An incorrect initialization order could lead to built-in drivers that
use the buddy allocator to run into NULL pointer dereferences due to
slab_blocks being uninitialized.

Fixes: 6387a3c4b0c4 ("drm: move the buddy allocator from i915 into common drm")
Fixes: ba110db8e1bc ("gpu: Move DRM buddy allocator one level up (part two)")
Cc: Joel Fernandes <joelagnelf@nvidia.com>
Cc: Dave Airlie <airlied@redhat.com>
Cc: Matthew Auld <matthew.auld@intel.com>
Cc: Peter Senna Tschudin <peter.senna@linux.intel.com>
Cc: intel-xe@lists.freedesktop.org
Cc: stable@vger.kernel.org
Reviewed-by: Joel Fernandes <joelagnelf@nvidia.com>
Signed-off-by: Koen Koning <koen.koning@linux.intel.com>
---
 drivers/gpu/buddy.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/gpu/buddy.c b/drivers/gpu/buddy.c
index 603c59a2013a..81f57fdf913b 100644
--- a/drivers/gpu/buddy.c
+++ b/drivers/gpu/buddy.c
@@ -1315,7 +1315,7 @@ static int __init gpu_buddy_module_init(void)
 	return 0;
 }

-module_init(gpu_buddy_module_init);
+subsys_initcall(gpu_buddy_module_init);
 module_exit(gpu_buddy_module_exit);

 MODULE_DESCRIPTION("GPU Buddy Allocator");
--
2.48.1


       reply	other threads:[~2026-02-19 21:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20260216111902.110286-1-koen.koning@linux.intel.com>
     [not found] ` <20260219213858.370675-1-koen.koning@linux.intel.com>
2026-02-19 21:38   ` Koen Koning [this message]
2026-02-20  6:06     ` [PATCH v3 1/3] gpu/buddy: fix module_init() usage Greg KH
2026-02-20 10:17       ` Danilo Krummrich
2026-02-20 13:55         ` Joel Fernandes
2026-02-21  5:44           ` Greg KH
2026-02-23  0:49             ` Joel Fernandes
2026-02-23 11:17               ` Koen Koning
2026-02-23 11:20                 ` Danilo Krummrich
2026-02-23 13:42                   ` Joel Fernandes
2026-02-23 22:31                   ` Danilo Krummrich
2026-02-24  3:41                     ` David Airlie
2026-02-19 21:38   ` [PATCH v3 2/3] drm/sched: " Koen Koning
2026-02-20  6:06     ` Greg KH

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=20260219213858.370675-2-koen.koning@linux.intel.com \
    --to=koen.koning@linux.intel.com \
    --cc=airlied@redhat.com \
    --cc=dakr@kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=joelagnelf@nvidia.com \
    --cc=matthew.auld@intel.com \
    --cc=peter.senna@linux.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