From: syzbot <syzbot+15cb24a539075fc4c472@syzkaller.appspotmail.com>
To: almaz.alexandrovich@paragon-software.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
llvm@lists.linux.dev, nathan@kernel.org,
ndesaulniers@google.com, ntfs3@lists.linux.dev,
syzkaller-bugs@googlegroups.com, trix@redhat.com,
viro@zeniv.linux.org.uk
Subject: Re: [syzbot] invalid opcode in writeback_single_inode
Date: Sun, 02 Oct 2022 11:22:35 -0700 [thread overview]
Message-ID: <000000000000adeda005ea114fea@google.com> (raw)
In-Reply-To: <00000000000042a5d005e967cd34@google.com>
syzbot has found a reproducer for the following issue on:
HEAD commit: b357fd1c2afc Merge tag 'usb-6.0-final' of git://git.kernel..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1563ce14880000
kernel config: https://syzkaller.appspot.com/x/.config?x=755695d26ad09807
dashboard link: https://syzkaller.appspot.com/bug?extid=15cb24a539075fc4c472
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=155d3a82880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11106dec880000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/9c8cf859a872/disk-b357fd1c.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/c1d370ace8a8/vmlinux-b357fd1c.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+15cb24a539075fc4c472@syzkaller.appspotmail.com
loop0: detected capacity change from 0 to 8226
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 3881 Comm: syz-executor338 Not tainted 6.0.0-rc7-syzkaller-00239-gb357fd1c2afc #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/22/2022
RIP: 0010:spin_unlock include/linux/spinlock.h:389 [inline]
RIP: 0010:writeback_single_inode+0x137/0x4c0 fs/fs-writeback.c:1728
Code: 8e 66 03 00 00 41 8b 5c 24 20 bf 01 00 00 00 89 de e8 ed 49 98 ff 83 fb 01 74 22 45 31 ff e8 20 4d 98 ff 4c 89 f7 e8 18 a8 9f <07> 44 89 f8 48 83 c4 08 5b 5d 41 5c 41 5d 41 5e 41 5f c3 e8 01 4d
RSP: 0018:ffffc90003c7fa10 EFLAGS: 00010286
RAX: 0000000080000000 RBX: 0000000000000010 RCX: 0000000000000000
RDX: 0000000000000001 RSI: 0000000000000004 RDI: 0000000000000001
RBP: ffff888071de4c10 R08: 0000000000000000 R09: ffff888071de4c9b
R10: ffffed100e3bc993 R11: 0000000000000000 R12: ffffc90003c7fa88
R13: ffff888071de4ce8 R14: ffff888071de4c98 R15: 0000000000000000
FS: 0000555556bc6300(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020003580 CR3: 0000000074274000 CR4: 0000000000350ee0
Call Trace:
<TASK>
write_inode_now+0x16a/0x1e0 fs/fs-writeback.c:2723
iput_final fs/inode.c:1735 [inline]
iput.part.0+0x45b/0x810 fs/inode.c:1774
iput+0x58/0x70 fs/inode.c:1764
ntfs_fill_super+0x2e89/0x37f0 fs/ntfs3/super.c:1190
get_tree_bdev+0x440/0x760 fs/super.c:1323
vfs_get_tree+0x89/0x2f0 fs/super.c:1530
do_new_mount fs/namespace.c:3040 [inline]
path_mount+0x1326/0x1e20 fs/namespace.c:3370
do_mount fs/namespace.c:3383 [inline]
__do_sys_mount fs/namespace.c:3591 [inline]
__se_sys_mount fs/namespace.c:3568 [inline]
__x64_sys_mount+0x27f/0x300 fs/namespace.c:3568
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fb0e371181a
Code: 48 c7 c2 c0 ff ff ff f7 d8 64 89 02 b8 ff ff ff ff eb d2 e8 a8 00 00 00 0f 1f 84 00 00 00 00 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 c0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffc5d57af98 EFLAGS: 00000286 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00007fb0e371181a
RDX: 0000000020000000 RSI: 0000000020000100 RDI: 00007ffc5d57afb0
RBP: 00007ffc5d57afb0 R08: 00007ffc5d57aff0 R09: 0000555556bc62c0
R10: 0000000000000000 R11: 0000000000000286 R12: 0000000000000004
R13: 00007ffc5d57aff0 R14: 0000000000000015 R15: 0000000020000db8
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:spin_unlock include/linux/spinlock.h:389 [inline]
RIP: 0010:writeback_single_inode+0x137/0x4c0 fs/fs-writeback.c:1728
Code: 8e 66 03 00 00 41 8b 5c 24 20 bf 01 00 00 00 89 de e8 ed 49 98 ff 83 fb 01 74 22 45 31 ff e8 20 4d 98 ff 4c 89 f7 e8 18 a8 9f <07> 44 89 f8 48 83 c4 08 5b 5d 41 5c 41 5d 41 5e 41 5f c3 e8 01 4d
RSP: 0018:ffffc90003c7fa10 EFLAGS: 00010286
RAX: 0000000080000000 RBX: 0000000000000010 RCX: 0000000000000000
RDX: 0000000000000001 RSI: 0000000000000004 RDI: 0000000000000001
RBP: ffff888071de4c10 R08: 0000000000000000 R09: ffff888071de4c9b
R10: ffffed100e3bc993 R11: 0000000000000000 R12: ffffc90003c7fa88
R13: ffff888071de4ce8 R14: ffff888071de4c98 R15: 0000000000000000
FS: 0000555556bc6300(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fb0e3740230 CR3: 0000000074274000 CR4: 0000000000350ef0
prev parent reply other threads:[~2022-10-02 18:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-24 8:08 [syzbot] invalid opcode in writeback_single_inode syzbot
2022-10-02 18:22 ` syzbot [this message]
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=000000000000adeda005ea114fea@google.com \
--to=syzbot+15cb24a539075fc4c472@syzkaller.appspotmail.com \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=ntfs3@lists.linux.dev \
--cc=syzkaller-bugs@googlegroups.com \
--cc=trix@redhat.com \
--cc=viro@zeniv.linux.org.uk \
/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.