mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: syzbot <syzbot+30eac43568e2b3d65728@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, linmiaohe@huawei.com,
	 linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	 syzkaller-bugs@googlegroups.com, vitaly.wool@konsulko.com
Subject: Re: [syzbot] [mm?] BUG: corrupted list in add_to_unbuddied
Date: Tue, 15 Oct 2024 07:52:25 -0700	[thread overview]
Message-ID: <670e81a9.050a0220.d9b66.0153.GAE@google.com> (raw)
In-Reply-To: <000000000000c6b91e0621a312f4@google.com>

syzbot has found a reproducer for the following issue on:

HEAD commit:    eca631b8fe80 Merge tag 'f2fs-6.12-rc4' of git://git.kernel..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14d0845f980000
kernel config:  https://syzkaller.appspot.com/x/.config?x=cfbd94c114a3d407
dashboard link: https://syzkaller.appspot.com/bug?extid=30eac43568e2b3d65728
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=16df4c40580000

Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/7feb34a89c2a/non_bootable_disk-eca631b8.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/830e1433408d/vmlinux-eca631b8.xz
kernel image: https://storage.googleapis.com/syzbot-assets/5538dfbaa4ef/bzImage-eca631b8.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/66bf3424533c/mount_0.gz

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

list_add corruption. next->prev should be prev (ffffe8ffffc31ed0), but was ffff88803ccdc800. (next=ffff88801e21b400).
------------[ cut here ]------------
kernel BUG at lib/list_debug.c:31!
Oops: invalid opcode: 0000 [#1] PREEMPT SMP KASAN NOPTI
CPU: 0 UID: 0 PID: 11 Comm: kworker/u4:0 Not tainted 6.12.0-rc3-syzkaller-00013-geca631b8fe80 #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014
Workqueue: zswap1 compact_page_work
RIP: 0010:__list_add_valid_or_report+0xd6/0xf0 lib/list_debug.c:29
Code: e8 1f 26 00 07 90 0f 0b 48 c7 c7 00 fe 60 8c e8 10 26 00 07 90 0f 0b 48 c7 c7 60 fe 60 8c 4c 89 e6 4c 89 f1 e8 fb 25 00 07 90 <0f> 0b 48 c7 c7 e0 fe 60 8c 4c 89 f6 4c 89 e1 e8 e6 25 00 07 90 0f
RSP: 0000:ffffc900003d7ad0 EFLAGS: 00010246
RAX: 0000000000000075 RBX: ffff88801e21b408 RCX: 18a79d2c00c9a300
RDX: 0000000000000000 RSI: 0000000000000002 RDI: 0000000000000000
RBP: ffffe8ffffc31ed0 R08: ffffffff8174afec R09: 1ffff9200007aef4
R10: dffffc0000000000 R11: fffff5200007aef5 R12: ffffe8ffffc31ed0
R13: dffffc0000000000 R14: ffff88801e21b400 R15: ffff8880400e6000
FS:  0000000000000000(0000) GS:ffff88801fc00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000c001e70000 CR3: 000000003dd36000 CR4: 0000000000352ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 __list_add_valid include/linux/list.h:88 [inline]
 __list_add include/linux/list.h:150 [inline]
 list_add include/linux/list.h:169 [inline]
 add_to_unbuddied+0x2e4/0x4d0 mm/z3fold.c:550
 do_compact_page+0x924/0xc50 mm/z3fold.c:772
 process_one_work kernel/workqueue.c:3229 [inline]
 process_scheduled_works+0xa63/0x1850 kernel/workqueue.c:3310
 worker_thread+0x870/0xd30 kernel/workqueue.c:3391
 kthread+0x2f0/0x390 kernel/kthread.c:389
 ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
 </TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:__list_add_valid_or_report+0xd6/0xf0 lib/list_debug.c:29
Code: e8 1f 26 00 07 90 0f 0b 48 c7 c7 00 fe 60 8c e8 10 26 00 07 90 0f 0b 48 c7 c7 60 fe 60 8c 4c 89 e6 4c 89 f1 e8 fb 25 00 07 90 <0f> 0b 48 c7 c7 e0 fe 60 8c 4c 89 f6 4c 89 e1 e8 e6 25 00 07 90 0f
RSP: 0000:ffffc900003d7ad0 EFLAGS: 00010246
RAX: 0000000000000075 RBX: ffff88801e21b408 RCX: 18a79d2c00c9a300
RDX: 0000000000000000 RSI: 0000000000000002 RDI: 0000000000000000
RBP: ffffe8ffffc31ed0 R08: ffffffff8174afec R09: 1ffff9200007aef4
R10: dffffc0000000000 R11: fffff5200007aef5 R12: ffffe8ffffc31ed0
R13: dffffc0000000000 R14: ffff88801e21b400 R15: ffff8880400e6000
FS:  0000000000000000(0000) GS:ffff88801fc00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000c001e70000 CR3: 000000003dd36000 CR4: 0000000000352ef0
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.

  reply	other threads:[~2024-10-15 14:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-08 22:22 syzbot
2024-10-15 14:52 ` syzbot [this message]
2024-10-15 22:39   ` Andrew Morton
2024-10-16  6:19     ` Aleksandr Nogikh
2024-10-16 21:37       ` Andrew Morton
2024-10-18  7:56         ` Aleksandr Nogikh

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=670e81a9.050a0220.d9b66.0153.GAE@google.com \
    --to=syzbot+30eac43568e2b3d65728@syzkaller.appspotmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linmiaohe@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=vitaly.wool@konsulko.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

all inboxes | Powered by JetHome®