From: syzbot <syzbot+c4b312367c177af55bdd@syzkaller.appspotmail.com>
To: konishi.ryusuke@gmail.com, linux-kernel@vger.kernel.org,
linux-nilfs@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: [syzbot] [nilfs?] WARNING: ODEBUG bug in nilfs_detach_log_writer
Date: Fri, 11 Oct 2024 03:17:22 -0700 [thread overview]
Message-ID: <6708fb32.050a0220.4cbc0.0001.GAE@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 0c559323bbaa Merge tag 'rust-fixes-6.12' of https://github..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=11c2ab9f980000
kernel config: https://syzkaller.appspot.com/x/.config?x=f95955e3f7b5790c
dashboard link: https://syzkaller.appspot.com/bug?extid=c4b312367c177af55bdd
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/f047d65a1c98/disk-0c559323.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/b9422453b274/vmlinux-0c559323.xz
kernel image: https://storage.googleapis.com/syzbot-assets/cbd997d77332/bzImage-0c559323.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+c4b312367c177af55bdd@syzkaller.appspotmail.com
NILFS (loop1): disposed unprocessed dirty file(s) when stopping log writer
------------[ cut here ]------------
ODEBUG: free active (active state 0) object: ffff88804a135270 object type: timer_list hint: nilfs_construction_timeout+0x0/0x40
WARNING: CPU: 1 PID: 10509 at lib/debugobjects.c:517 debug_print_object+0x17a/0x1f0 lib/debugobjects.c:514
Modules linked in:
CPU: 1 UID: 0 PID: 10509 Comm: syz-executor Not tainted 6.12.0-rc1-syzkaller-00125-g0c559323bbaa #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
RIP: 0010:debug_print_object+0x17a/0x1f0 lib/debugobjects.c:514
Code: e8 3b 45 3c fd 4c 8b 0b 48 c7 c7 20 02 61 8c 48 8b 74 24 08 48 89 ea 44 89 e1 4d 89 f8 ff 34 24 e8 7b 88 93 fc 48 83 c4 08 90 <0f> 0b 90 90 ff 05 64 ca 5a 0b 48 83 c4 10 5b 41 5c 41 5d 41 5e 41
RSP: 0018:ffffc90003d87958 EFLAGS: 00010282
RAX: 82bf3185606fc400 RBX: ffffffff8c0cd900 RCX: ffff88802c7a8000
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000
RBP: ffffffff8c6103a0 R08: ffffffff8155daa2 R09: fffffbfff1cf9fd8
R10: dffffc0000000000 R11: fffffbfff1cf9fd8 R12: 0000000000000000
R13: ffffffff8c6102b8 R14: dffffc0000000000 R15: ffff88804a135270
FS: 000055558707b500(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00005555870965c8 CR3: 00000000549d4000 CR4: 0000000000350ef0
Call Trace:
<TASK>
__debug_check_no_obj_freed lib/debugobjects.c:989 [inline]
debug_check_no_obj_freed+0x45b/0x580 lib/debugobjects.c:1019
slab_free_hook mm/slub.c:2274 [inline]
slab_free mm/slub.c:4580 [inline]
kfree+0x11f/0x440 mm/slub.c:4728
nilfs_segctor_destroy fs/nilfs2/segment.c:2828 [inline]
nilfs_detach_log_writer+0x754/0xa50 fs/nilfs2/segment.c:2893
nilfs_put_super+0x4d/0x160 fs/nilfs2/super.c:503
generic_shutdown_super+0x13b/0x2d0 fs/super.c:642
kill_block_super+0x44/0x90 fs/super.c:1696
deactivate_locked_super+0xc6/0x130 fs/super.c:473
cleanup_mnt+0x41f/0x4b0 fs/namespace.c:1373
task_work_run+0x251/0x310 kernel/task_work.c:228
resume_user_mode_work include/linux/resume_user_mode.h:50 [inline]
exit_to_user_mode_loop kernel/entry/common.c:114 [inline]
exit_to_user_mode_prepare include/linux/entry-common.h:328 [inline]
__syscall_exit_to_user_mode_work kernel/entry/common.c:207 [inline]
syscall_exit_to_user_mode+0x168/0x370 kernel/entry/common.c:218
do_syscall_64+0x100/0x230 arch/x86/entry/common.c:89
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f95d657f327
Code: a8 ff ff ff f7 d8 64 89 01 48 83 c8 ff c3 0f 1f 44 00 00 31 f6 e9 09 00 00 00 66 0f 1f 84 00 00 00 00 00 b8 a6 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 01 c3 48 c7 c2 a8 ff ff ff f7 d8 64 89 02 b8
RSP: 002b:00007ffd4adf5dc8 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 00007f95d657f327
RDX: 0000000000000000 RSI: 0000000000000009 RDI: 00007ffd4adf5e80
RBP: 00007ffd4adf5e80 R08: 0000000000000000 R09: 0000000000000000
R10: 00000000ffffffff R11: 0000000000000246 R12: 00007ffd4adf6f00
R13: 00007f95d65f0134 R14: 0000000000110fcd R15: 00007ffd4adf6f40
</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@googlegroups.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
reply other threads:[~2024-10-11 10:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=6708fb32.050a0220.4cbc0.0001.GAE@google.com \
--to=syzbot+c4b312367c177af55bdd@syzkaller.appspotmail.com \
--cc=konishi.ryusuke@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nilfs@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.