public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+b2e951687503f32f74ce@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [dri?] KASAN: slab-use-after-free Read in drm_gem_object_release_handle
Date: Thu, 16 Apr 2026 02:03:01 -0700	[thread overview]
Message-ID: <69e0a5c5.a70a0220.259bc5.001e.GAE@google.com> (raw)
In-Reply-To: <20260416082000.1950-1-hdanton@sina.com>

Hello,

syzbot has tested the proposed patch and the reproducer did not trigger any issue:

Reported-by: syzbot+b2e951687503f32f74ce@syzkaller.appspotmail.com
Tested-by: syzbot+b2e951687503f32f74ce@syzkaller.appspotmail.com

Tested on:

commit:         1d51b370 Merge tag 'jfs-7.1' of github.com:kleikamp/li..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=10b5e906580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=769ed9499e4e3d7d
dashboard link: https://syzkaller.appspot.com/bug?extid=b2e951687503f32f74ce
compiler:       Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
patch:          https://syzkaller.appspot.com/x/patch.diff?x=154398ce580000

Note: testing is done by a robot and is best-effort only.

  reply	other threads:[~2026-04-16  9:03 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-13 17:16 [syzbot] [dri?] KASAN: slab-use-after-free Read in drm_gem_object_release_handle syzbot
2026-04-14  0:16 ` Forwarded: [PATCH] drm/gem: fix use-after-free in drm_gem_release syzbot
2026-04-14  1:32 ` syzbot
2026-04-14  5:00 ` [syzbot] [dri?] KASAN: slab-use-after-free Read in drm_gem_object_release_handle Hillf Danton
2026-04-14  5:26   ` syzbot
2026-04-14  5:49 ` Forwarded: [PATCH] drm/gem: fix use-after-free in drm_gem_release syzbot
2026-04-14  8:46 ` [syzbot] [dri?] KASAN: slab-use-after-free Read in drm_gem_object_release_handle Hillf Danton
2026-04-14  9:04   ` syzbot
2026-04-14 10:03 ` Hillf Danton
2026-04-14 10:20   ` syzbot
2026-04-15  0:33 ` Hillf Danton
2026-04-15  3:54   ` syzbot
2026-04-15  7:50 ` Hillf Danton
2026-04-15  8:50   ` syzbot
2026-04-15 11:19 ` Hillf Danton
2026-04-15 11:44   ` syzbot
2026-04-16  0:44 ` Hillf Danton
2026-04-16  4:52   ` syzbot
2026-04-16  2:59 ` Edward Adam Davis
2026-04-16  5:13   ` syzbot
2026-04-16  8:19 ` Hillf Danton
2026-04-16  9:03   ` syzbot [this message]
2026-04-16  8:57 ` [PATCH] drm: Avoid the chaotic interleaving of change and delete handle Edward Adam Davis
     [not found] <20260414001626.60471-1-kartikey406@gmail.com>
2026-04-14  0:36 ` [syzbot] [dri?] KASAN: slab-use-after-free Read in drm_gem_object_release_handle syzbot
     [not found] <20260414013225.64095-1-kartikey406@gmail.com>
2026-04-14  1:50 ` syzbot
     [not found] <20260414054951.69728-1-kartikey406@gmail.com>
2026-04-14  6:22 ` syzbot

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=69e0a5c5.a70a0220.259bc5.001e.GAE@google.com \
    --to=syzbot+b2e951687503f32f74ce@syzkaller.appspotmail.com \
    --cc=hdanton@sina.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzkaller-bugs@googlegroups.com \
    /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