From: syzbot <syzbot+42a37bf8045847d8f9d2@syzkaller.appspotmail.com>
To: agruenba@redhat.com, anprice@redhat.com, gfs2@lists.linux.dev,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [gfs2?] KASAN: slab-use-after-free Write in gfs2_qd_dealloc (3)
Date: Thu, 24 Jul 2025 04:57:03 -0700 [thread overview]
Message-ID: <68821f8f.a00a0220.2f88df.0024.GAE@google.com> (raw)
In-Reply-To: <3d164a94-b643-411b-9f22-3bb02af4e4f0@redhat.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
WARNING in move_to_new_folio
------------[ cut here ]------------
gfs2_meta_aops does not implement migrate_folio
WARNING: CPU: 0 PID: 30 at mm/migrate.c:944 fallback_migrate_folio mm/migrate.c:942 [inline]
WARNING: CPU: 0 PID: 30 at mm/migrate.c:944 move_to_new_folio+0x696/0x7a0 mm/migrate.c:996
Modules linked in:
CPU: 0 UID: 0 PID: 30 Comm: kcompactd1 Not tainted 6.16.0-rc7-syzkaller-g25fae0b93d1d-dirty #0 PREEMPT(full)
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014
RIP: 0010:fallback_migrate_folio mm/migrate.c:942 [inline]
RIP: 0010:move_to_new_folio+0x696/0x7a0 mm/migrate.c:996
Code: 0d 01 90 42 80 7c 3d 00 00 74 0a 48 8b 7c 24 20 e8 2f 53 fe ff 48 8b 44 24 20 48 8b 30 48 c7 c7 20 bb 97 8b e8 bb b7 5e ff 90 <0f> 0b 90 90 49 bf 00 00 00 00 00 fc ff df e9 7e fd ff ff e8 62 d2
RSP: 0018:ffffc90000516fd0 EFLAGS: 00010246
RAX: daec11f2299abc00 RBX: ffffea000100abc0 RCX: ffff888030f88000
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000002
RBP: 1ffff1100887b921 R08: 0000000000000003 R09: 0000000000000004
R10: dffffc0000000000 R11: fffffbfff1bfaa6c R12: ffffea00014e3d40
R13: ffff8880443dc7e8 R14: ffffea000100abc8 R15: dffffc0000000000
FS: 0000000000000000(0000) GS:ffff88808d218000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fce2e39a000 CR3: 0000000057fda000 CR4: 0000000000352ef0
Call Trace:
<TASK>
migrate_folio_move mm/migrate.c:1301 [inline]
migrate_folios_move mm/migrate.c:1653 [inline]
migrate_pages_batch+0x1c34/0x2830 mm/migrate.c:1900
migrate_pages_sync mm/migrate.c:1930 [inline]
migrate_pages+0x1bcc/0x2930 mm/migrate.c:2039
compact_zone+0x23f4/0x4ad0 mm/compaction.c:2683
compact_node+0x1d2/0x280 mm/compaction.c:2952
kcompactd+0xbc8/0x1290 mm/compaction.c:3250
kthread+0x70e/0x8a0 kernel/kthread.c:464
ret_from_fork+0x3fc/0x770 arch/x86/kernel/process.c:148
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
</TASK>
Tested on:
commit: 25fae0b9 Merge tag 'drm-fixes-2025-07-24' of https://g..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=12eac0a2580000
kernel config: https://syzkaller.appspot.com/x/.config?x=8adfe52da0de2761
dashboard link: https://syzkaller.appspot.com/bug?extid=42a37bf8045847d8f9d2
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
patch: https://syzkaller.appspot.com/x/patch.diff?x=118ee0a2580000
next prev parent reply other threads:[~2025-07-24 11:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-28 10:08 [syzbot] [gfs2?] KASAN: slab-use-after-free Write in gfs2_qd_dealloc (3) syzbot
2025-07-23 20:49 ` syzbot
2025-07-24 11:38 ` Andrew Price
2025-07-24 11:57 ` syzbot [this message]
2025-07-24 12:11 ` Andrew Price
2026-04-30 11:25 ` Forwarded: " syzbot
2026-04-30 22:30 ` syzbot
[not found] <177754835224.2147696.8354228851433174481@gmail.com>
2026-04-30 12:51 ` syzbot
[not found] <177758824329.163667.6298575861470288172@gmail.com>
2026-04-30 23:05 ` 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=68821f8f.a00a0220.2f88df.0024.GAE@google.com \
--to=syzbot+42a37bf8045847d8f9d2@syzkaller.appspotmail.com \
--cc=agruenba@redhat.com \
--cc=anprice@redhat.com \
--cc=gfs2@lists.linux.dev \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.