[v6.1] kernel BUG in dnotify_free_mark

0 views
Skip to first unread message

syzbot

unread,
Jul 30, 2023, 3:52:58 AM7/30/23
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: d2a6dc4eaf6d Linux 6.1.42
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1500e516a80000
kernel config: https://syzkaller.appspot.com/x/.config?x=54d239cfb343e1e3
dashboard link: https://syzkaller.appspot.com/bug?extid=2f4aa3239150dd006e44
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=173c6181a80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15e8a009a80000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/48a245e1f181/disk-d2a6dc4e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/36fe96f5b416/vmlinux-d2a6dc4e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/d53f0286f35a/bzImage-d2a6dc4e.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/06cedf9088ec/mount_0.gz

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

------------[ cut here ]------------
kernel BUG at fs/notify/dnotify/dnotify.c:136!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 34 Comm: kworker/u4:2 Not tainted 6.1.42-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2023
Workqueue: events_unbound fsnotify_mark_destroy_workfn
RIP: 0010:dnotify_free_mark+0x53/0x60 fs/notify/dnotify/dnotify.c:136
Code: 48 89 df e8 6f 42 de ff 48 83 3b 00 75 17 e8 14 b7 87 ff 48 8b 3d fd 67 71 0c 4c 89 f6 5b 41 5e e9 12 71 dd ff e8 fd b6 87 ff <0f> 0b cc cc cc cc cc cc cc cc cc cc cc 55 41 57 41 56 41 55 41 54
RSP: 0018:ffffc90000ab7b88 EFLAGS: 00010293
RAX: ffffffff820233b3 RBX: ffff888079909080 RCX: ffff8880152c3b80
RDX: 0000000000000000 RSI: 0000000000000017 RDI: ffff888079909000
RBP: ffffc90000ab7c50 R08: ffffffff8201a47b R09: ffffed100f85f002
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff888145681800
R13: ffffc90000ab7be0 R14: ffff888079909000 R15: ffff888079909000
FS: 0000000000000000(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055fff7e8c7a8 CR3: 000000001b37f000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
fsnotify_final_mark_destroy fs/notify/mark.c:278 [inline]
fsnotify_mark_destroy_workfn+0x2c7/0x340 fs/notify/mark.c:902
process_one_work+0x8aa/0x11f0 kernel/workqueue.c:2292
worker_thread+0xa5f/0x1210 kernel/workqueue.c:2439
kthread+0x26e/0x300 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:dnotify_free_mark+0x53/0x60 fs/notify/dnotify/dnotify.c:136


---
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 syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title

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.

If you want to change bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the bug is a duplicate of another bug, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

syzbot

unread,
Nov 23, 2023, 12:35:07 PM11/23/23
to syzkaller...@googlegroups.com
syzbot suspects this issue could be fixed by backporting the following commit:

commit 4ad5c924df6cd6d85708fa23f9d9a2b78a2e428e
git tree: upstream
Author: Konstantin Komarov <almaz.ale...@paragon-software.com>
Date: Fri Sep 22 10:07:59 2023 +0000

fs/ntfs3: Allow repeated call to ntfs3_put_sbi

bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=152d8d67680000
Please keep in mind that other backports might be required as well.

For information about bisection process see: https://goo.gl/tpsmEJ#bisection
Reply all
Reply to author
Forward
0 new messages