linux-kernel - Re: [git pull] drm for 6.19-rc1

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAHk-=whaiMayMx=LrL7P119MLBX6exM_mEu4S2uBRT+xWQ-mbA@mail.gmail.com>
Date: Thu, 4 Dec 2025 09:35:24 -0800
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Dave Airlie <airlied@...il.com>, Matthew Brost <matthew.brost@...el.com>, 
	Thomas Hellström <thomas.hellstrom@...ux.intel.com>, 
	Jouni Högander <jouni.hogander@...el.com>, 
	Matt Roper <matthew.d.roper@...el.com>
Cc: Simona Vetter <simona@...ll.ch>, dri-devel <dri-devel@...ts.freedesktop.org>, 
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [git pull] drm for 6.19-rc1

On Tue, 2 Dec 2025 at 23:23, Dave Airlie <airlied@...il.com> wrote:
>
> This is the main drm pull request for 6.19.

I have pulled this and pushed out the result. It "works" for me on my
Xe setup, but I do get a new refcount warning, which looks like
something might be seriously wrong.

(Side note: I'm also running with

  https://lore.kernel.org/all/20251119153321.2640969-1-jani.nikula@intel.com/

fixed up for the merge and applied to make my dual 6k monitor setup happy).

I get this:

  refcount_t: underflow; use-after-free.
  WARNING: lib/refcount.c:28 at 0x0, CPU#43: gst-plugin-scan/2770
  Modules linked in: rfcomm sunrpc nf_conntrack_netbios_ns ...
  CPU: 43 UID: 60578 PID: 2770 Comm: gst-plugin-scan Not tainted
6.18.0-06709-gab59a11f1240 #25 PREEMPTLAZY
  Hardware name: Gigabyte Technology Co., Ltd. TRX40 AORUS
MASTER/TRX40 AORUS MASTER, BIOS F7 09/07/2022
  RIP: 0010:refcount_warn_saturate+0x42/0x70
  ...
  Call Trace:
   xe_exec_queue_destroy+0x1be/0x1d0 [xe]
   xe_vm_close_and_put+0x3b8/0x770 [xe]
   xe_vm_destroy_ioctl+0x107/0x180 [xe]
   drm_ioctl_kernel+0xa3/0xd0 [drm]
   drm_ioctl+0x30f/0x470 [drm]
   xe_drm_ioctl+0x48/0x70 [xe]
   __se_sys_ioctl+0x6d/0xb0
   do_syscall_64+0x6a/0x260
   entry_SYSCALL_64_after_hwframe+0x4b/0x53

which hopefully gives somebody an idea.

Added Xe people involved with recent commits to the participants.

Anybody?

             Linus