mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: "Linus Torvalds" <torvalds@linux-foundation.org>,
	"Dave Airlie" <airlied@gmail.com>,
	"Matthew Brost" <matthew.brost@intel.com>,
	"Jouni Högander" <jouni.hogander@intel.com>,
	"Matt Roper" <matthew.d.roper@intel.com>
Cc: Simona Vetter <simona@ffwll.ch>,
	dri-devel <dri-devel@lists.freedesktop.org>,
	 LKML <linux-kernel@vger.kernel.org>
Subject: Re: [git pull] drm for 6.19-rc1
Date: Thu, 04 Dec 2025 18:50:11 +0100	[thread overview]
Message-ID: <cfe36079c764e984e9719a8d398f4ffc074a6ae7.camel@linux.intel.com> (raw)
In-Reply-To: <CAHk-=whaiMayMx=LrL7P119MLBX6exM_mEu4S2uBRT+xWQ-mbA@mail.gmail.com>

Hi, Linus,

On Thu, 2025-12-04 at 09:35 -0800, Linus Torvalds wrote:
> On Tue, 2 Dec 2025 at 23:23, Dave Airlie <airlied@gmail.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.

Looks like a backmerge gone wrong and duplicating a put.

We'll pick that up and try to provide a fix ASAP.

Thanks,
Thomas


> 
> Added Xe people involved with recent commits to the participants.
> 
> Anybody?
> 
>              Linus


      reply	other threads:[~2025-12-04 17:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-03  7:22 Dave Airlie
2025-12-04 17:31 ` pr-tracker-bot
2025-12-04 17:35 ` Linus Torvalds
2025-12-04 17:50   ` Thomas Hellström [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=cfe36079c764e984e9719a8d398f4ffc074a6ae7.camel@linux.intel.com \
    --to=thomas.hellstrom@linux.intel.com \
    --cc=airlied@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jouni.hogander@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew.brost@intel.com \
    --cc=matthew.d.roper@intel.com \
    --cc=simona@ffwll.ch \
    --cc=torvalds@linux-foundation.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

all inboxes | Powered by JetHome®