All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+d34c2a269ed512c531b0@syzkaller.appspotmail.com>
To: agruenba@redhat.com, gfs2@lists.linux.dev, hdanton@sina.com,
	 linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [gfs2?] BUG: corrupted list in gfs2_fill_super
Date: Thu, 11 Jul 2024 04:00:28 -0700	[thread overview]
Message-ID: <000000000000bb1365061cf6ab5b@google.com> (raw)
In-Reply-To: <0000000000002501960619e2366b@google.com>

syzbot has found a reproducer for the following issue on:

HEAD commit:    523b23f0bee3 Add linux-next specific files for 20240710
git tree:       linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=100b427e980000
kernel config:  https://syzkaller.appspot.com/x/.config?x=98dd8c4bab5cdce
dashboard link: https://syzkaller.appspot.com/bug?extid=d34c2a269ed512c531b0
compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=16907bb9980000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=10ce66a5980000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/345bcd25ed2f/disk-523b23f0.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/a4508962d345/vmlinux-523b23f0.xz
kernel image: https://storage.googleapis.com/syzbot-assets/4ba5eb555639/bzImage-523b23f0.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/65bde6695704/mount_3.gz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+d34c2a269ed512c531b0@syzkaller.appspotmail.com

list_del corruption, ffff88801e354410->prev is LIST_POISON2 (dead000000000122)
------------[ cut here ]------------
kernel BUG at lib/list_debug.c:61!
Oops: invalid opcode: 0000 [#1] PREEMPT SMP KASAN PTI
CPU: 1 UID: 0 PID: 5777 Comm: syz-executor410 Not tainted 6.10.0-rc7-next-20240710-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/07/2024
RIP: 0010:__list_del_entry_valid_or_report+0x106/0x140 lib/list_debug.c:59
Code: e8 af 5f d8 06 90 0f 0b 48 c7 c7 80 a0 20 8c 4c 89 fe e8 9d 5f d8 06 90 0f 0b 48 c7 c7 e0 a0 20 8c 4c 89 fe e8 8b 5f d8 06 90 <0f> 0b 48 c7 c7 40 a1 20 8c 4c 89 fe 48 89 d9 e8 76 5f d8 06 90 0f
RSP: 0018:ffffc9000912f928 EFLAGS: 00010246
RAX: 000000000000004e RBX: dead000000000122 RCX: 710a8d5645865200
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: 1ffff11005f41d00 R08: ffffffff8173e319 R09: 1ffff92001225ec0
R10: dffffc0000000000 R11: fffff52001225ec1 R12: dffffc0000000000
R13: ffff88801e354400 R14: ffff88802c12a810 R15: ffff88801e354410
FS:  00007fcd932e66c0(0000) GS:ffff8880b9500000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00005555827377f8 CR3: 000000002046e000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 __list_del_entry_valid include/linux/list.h:124 [inline]
 __list_del_entry include/linux/list.h:215 [inline]
 list_del_rcu include/linux/rculist.h:157 [inline]
 destroy_workqueue+0x7b3/0xc40 kernel/workqueue.c:5847
 gfs2_fill_super+0x128a/0x2500 fs/gfs2/ops_fstype.c:1310
 get_tree_bdev+0x3f7/0x570 fs/super.c:1624
 gfs2_get_tree+0x54/0x220 fs/gfs2/ops_fstype.c:1329
 vfs_get_tree+0x90/0x2a0 fs/super.c:1789
 do_new_mount+0x2be/0xb40 fs/namespace.c:3471
 do_mount fs/namespace.c:3811 [inline]
 __do_sys_mount fs/namespace.c:4019 [inline]
 __se_sys_mount+0x2d6/0x3c0 fs/namespace.c:3996
 do_syscall_x64 arch/x86/entry/common.c:52 [inline]
 do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fcd9335b60a
Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb a6 e8 ee 08 00 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fcd932e5fd8 EFLAGS: 00000282 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007fcd932e5ff0 RCX: 00007fcd9335b60a
RDX: 00000000200124c0 RSI: 0000000020012500 RDI: 00007fcd932e5ff0
RBP: 0000000000000005 R08: 00007fcd932e6030 R09: 00000000000124a5
R10: 0000000000000800 R11: 0000000000000282 R12: 00007fcd932e6030
R13: 0000000000000800 R14: 0000000000000004 R15: 0000000001000000
 </TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:__list_del_entry_valid_or_report+0x106/0x140 lib/list_debug.c:59
Code: e8 af 5f d8 06 90 0f 0b 48 c7 c7 80 a0 20 8c 4c 89 fe e8 9d 5f d8 06 90 0f 0b 48 c7 c7 e0 a0 20 8c 4c 89 fe e8 8b 5f d8 06 90 <0f> 0b 48 c7 c7 40 a1 20 8c 4c 89 fe 48 89 d9 e8 76 5f d8 06 90 0f
RSP: 0018:ffffc9000912f928 EFLAGS: 00010246

RAX: 000000000000004e RBX: dead000000000122 RCX: 710a8d5645865200
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: 1ffff11005f41d00 R08: ffffffff8173e319 R09: 1ffff92001225ec0
R10: dffffc0000000000 R11: fffff52001225ec1 R12: dffffc0000000000
R13: ffff88801e354400 R14: ffff88802c12a810 R15: ffff88801e354410
FS:  00007fcd932e66c0(0000) GS:ffff8880b9500000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00005555827377f8 CR3: 000000002046e000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


---
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

  parent reply	other threads:[~2024-07-11 11:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-02  6:20 [syzbot] [gfs2?] BUG: corrupted list in gfs2_fill_super syzbot
2024-06-02  9:50 ` Hillf Danton
2024-06-02 10:23   ` syzbot
2024-07-11 11:00 ` syzbot [this message]
2024-07-21 22:11 ` 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=000000000000bb1365061cf6ab5b@google.com \
    --to=syzbot+d34c2a269ed512c531b0@syzkaller.appspotmail.com \
    --cc=agruenba@redhat.com \
    --cc=gfs2@lists.linux.dev \
    --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 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.