Message-ID: <CANp29Y5edqzjYyXEgeU8i9mrrfOkPBMWYd8yMnhrozePFuWhkA@mail.gmail.com>
Date: Mon, 2 Sep 2024 12:23:04 +0200
From: Aleksandr Nogikh <nogikh@...gle.com>
To: Qu Wenruo <quwenruo.btrfs@....com>
Cc: syzbot <syzbot+480676efc0c3a76b5214@...kaller.appspotmail.com>, clm@...com, 
	dsterba@...e.com, josef@...icpanda.com, linux-btrfs@...r.kernel.org, 
	linux-kernel@...r.kernel.org, syzkaller-bugs@...glegroups.com
Subject: Re: [syzbot] [btrfs?] WARNING in __btrfs_free_extent (3)

On Sun, Sep 1, 2024 at 12:33 AM 'Qu Wenruo' via syzkaller-bugs
<syzkaller-bugs@...glegroups.com> wrote:
>
>
>
> 在 2024/9/1 03:29, syzbot 写道:
> > Hello,
> >
> > syzbot found the following issue on:
> >
> > HEAD commit:    86987d84b968 Merge tag 'v6.11-rc5-client-fixes' of git://g..
> > git tree:       upstream
> > console output: https://syzkaller.appspot.com/x/log.txt?x=109f1425980000
>
> I was checking the console and trying to find out what's before the
> transaction abort.
>
> The error number means it's ENOENT thus it seems to be a missing extent
> item or whatever.
>
> But the console output contains not even the WARNING line, is the
> console output trimmed or whatever?

Yes, that output log was indeed too big and was just trimmed to fit in
the limits :/
I'll take a look into how we can handle it better on the syzbot side.

In the meanwhile, there are a few other console logs on the dashboard
[1] that were not trimmed and that contain the WARNING line. E.g.
https://syzkaller.appspot.com/text?tag=CrashLog&x=174d4215980000

[1] https://syzkaller.appspot.com/bug?extid=480676efc0c3a76b5214

-- 
Aleksandr

>
> Thanks,
> Qu
>
> > kernel config:  https://syzkaller.appspot.com/x/.config?x=a0455552d0b27491
> > dashboard link: https://syzkaller.appspot.com/bug?extid=480676efc0c3a76b5214
> > compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
> >
> > Unfortunately, I don't have any reproducer for this issue yet.
> >
> > Downloadable assets:
> > disk image: https://storage.googleapis.com/syzbot-assets/87692913ef45/disk-86987d84.raw.xz
> > vmlinux: https://storage.googleapis.com/syzbot-assets/a27da6973d7f/vmlinux-86987d84.xz
> > kernel image: https://storage.googleapis.com/syzbot-assets/2e28d02ce725/bzImage-86987d84.xz
> >
> > IMPORTANT: if you fix the issue, please add the following tag to the commit:
> > Reported-by: syzbot+480676efc0c3a76b5214@...kaller.appspotmail.com
> >
> > ------------[ cut here ]------------
> > BTRFS: Transaction aborted (error -2)
> > WARNING: CPU: 1 PID: 63 at fs/btrfs/extent-tree.c:2972 do_free_extent_accounting fs/btrfs/extent-tree.c:2972 [inline]
> > WARNING: CPU: 1 PID: 63 at fs/btrfs/extent-tree.c:2972 __btrfs_free_extent+0x32d1/0x3a10 fs/btrfs/extent-tree.c:3346
> > Modules linked in:
> > CPU: 1 UID: 0 PID: 63 Comm: kworker/u8:4 Not tainted 6.11.0-rc5-syzkaller-00057-g86987d84b968 #0
> > Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024
> > Workqueue: events_unbound btrfs_async_reclaim_metadata_space
> > RIP: 0010:do_free_extent_accounting fs/btrfs/extent-tree.c:2972 [inline]
> > RIP: 0010:__btrfs_free_extent+0x32d1/0x3a10 fs/btrfs/extent-tree.c:3346
> > Code: e8 24 a4 ae fd 90 0f 0b 90 90 e9 3c f3 ff ff e8 35 80 ec fd 90 48 c7 c7 00 79 2b 8c 44 8b 6c 24 18 44 89 ee e8 00 a4 ae fd 90 <0f> 0b 90 90 4c 8b 24 24 e9 4f f3 ff ff e8 0d 80 ec fd 90 48 c7 c7
> > RSP: 0018:ffffc900015e6f80 EFLAGS: 00010246
> > RAX: ec2b4374561a8400 RBX: ffff88805d790001 RCX: ffff888015581e00
> > RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000
> > RBP: ffffc900015e7150 R08: ffffffff8155b212 R09: fffffbfff1cba0e0
> > R10: dffffc0000000000 R11: fffffbfff1cba0e0 R12: dffffc0000000000
> > R13: 00000000fffffffe R14: 0000000000000000 R15: ffff88805d3be5c8
> > FS:  0000000000000000(0000) GS:ffff8880b9300000(0000) knlGS:0000000000000000
> > CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> > CR2: 00007f3dca9f0270 CR3: 000000002dd02000 CR4: 00000000003506f0
> > DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> > DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
> > Call Trace:
> >   <TASK>
> >   run_delayed_tree_ref fs/btrfs/extent-tree.c:1724 [inline]
> >   run_one_delayed_ref fs/btrfs/extent-tree.c:1750 [inline]
> >   btrfs_run_delayed_refs_for_head fs/btrfs/extent-tree.c:2015 [inline]
> >   __btrfs_run_delayed_refs+0x112e/0x4680 fs/btrfs/extent-tree.c:2085
> >   btrfs_run_delayed_refs+0xe3/0x2c0 fs/btrfs/extent-tree.c:2197
> >   btrfs_commit_transaction+0x4be/0x3740 fs/btrfs/transaction.c:2198
> >   flush_space+0x19c/0xd00 fs/btrfs/space-info.c:835
> >   btrfs_async_reclaim_metadata_space+0x6dc/0x840 fs/btrfs/space-info.c:1106
> >   process_one_work kernel/workqueue.c:3231 [inline]
> >   process_scheduled_works+0xa2c/0x1830 kernel/workqueue.c:3312
> >   worker_thread+0x86d/0xd10 kernel/workqueue.c:3389
> >   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>
> >
> >
> > ---
> > This report is generated by a bot. It may contain errors.
> > See https://goo.gl/tpsmEJ for more information about syzbot.
> > syzbot engineers can be reached at syzkaller@...glegroups.com.
> >
> > syzbot will keep track of this issue. See:
> > https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
> >
> > If the report is already addressed, let syzbot know by replying with:
> > #syz fix: exact-commit-title
> >
> > If you want to overwrite report's subsystems, reply with:
> > #syz set subsystems: new-subsystem
> > (See the list of subsystem names on the web dashboard)
> >
> > If the report is a duplicate of another one, reply with:
> > #syz dup: exact-subject-of-another-report
> >
> > If you want to undo deduplication, reply with:
> > #syz undup
> >
>

Powered by blists - more mailing lists