From: syzbot <syzbot+7e5cf1d80677ec185e63-Pl5Pbv+GP7P466ipTTIvnc23WoclnBCfAL8bYrjMMd8@public.gmane.org>
To: akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org,
konishi.ryusuke-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org,
linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
syzkaller-bugs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org,
willy-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org
Subject: [syzbot] [nilfs2?] kernel BUG in folio_end_writeback
Date: Mon, 26 Dec 2022 19:42:34 -0800 [thread overview]
Message-ID: <000000000000dc83d605f0c70a11@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 0a924817d2ed Merge tag '6.2-rc-smb3-client-fixes-part2' of..
git tree: upstream
console+strace: https://syzkaller.appspot.com/x/log.txt?x=16228274480000
kernel config: https://syzkaller.appspot.com/x/.config?x=4e2d7bfa2d6d5a76
dashboard link: https://syzkaller.appspot.com/bug?extid=7e5cf1d80677ec185e63
compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14494888480000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11c189f8480000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/b0959a409a79/disk-0a924817.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/388daa76797b/vmlinux-0a924817.xz
kernel image: https://storage.googleapis.com/syzbot-assets/b9d2d406c075/bzImage-0a924817.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/166e13821ab4/mount_0.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+7e5cf1d80677ec185e63-Pl5Pbv+GP7P466ipTTIvnc23WoclnBCfAL8bYrjMMd8@public.gmane.org
------------[ cut here ]------------
kernel BUG at mm/filemap.c:1615!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 15 Comm: ksoftirqd/0 Not tainted 6.1.0-syzkaller-14321-g0a924817d2ed #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
RIP: 0010:folio_end_writeback+0x34d/0x530 mm/filemap.c:1615
Code: 84 87 00 00 00 e8 13 5a d2 ff e9 36 fd ff ff e8 09 5a d2 ff 4c 89 f7 48 c7 c6 20 84 f8 8a e8 ca 3a 10 00 0f 0b e8 f3 59 d2 ff <0f> 0b e8 ec 59 d2 ff 4c 89 f7 48 c7 c6 60 86 f8 8a e8 ad 3a 10 00
RSP: 0018:ffffc90000147b88 EFLAGS: 00010246
RAX: ffffffff81b9813d RBX: 0000000000000082 RCX: ffff88813fefba80
RDX: 0000000080000100 RSI: ffffffff8aedcc60 RDI: ffffffff8b4bbfe0
RBP: 1ffffd40000ed426 R08: dffffc0000000000 R09: fffffbfff1d2cabe
R10: fffffbfff1d2cabe R11: 1ffffffff1d2cabd R12: ffffea000076a134
R13: dffffc0000000000 R14: ffffea000076a100 R15: 1ffffd40000ed420
FS: 0000000000000000(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ff727105718 CR3: 00000000291ab000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
end_bio_bh_io_sync+0xb1/0x110 fs/buffer.c:2655
req_bio_endio block/blk-mq.c:794 [inline]
blk_update_request+0x51c/0x1040 block/blk-mq.c:926
blk_mq_end_request+0x39/0x70 block/blk-mq.c:1053
blk_complete_reqs block/blk-mq.c:1131 [inline]
blk_done_softirq+0x119/0x160 block/blk-mq.c:1136
__do_softirq+0x277/0x738 kernel/softirq.c:571
run_ksoftirqd+0xa2/0x100 kernel/softirq.c:934
smpboot_thread_fn+0x533/0xa10 kernel/smpboot.c:164
kthread+0x266/0x300 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:folio_end_writeback+0x34d/0x530 mm/filemap.c:1615
Code: 84 87 00 00 00 e8 13 5a d2 ff e9 36 fd ff ff e8 09 5a d2 ff 4c 89 f7 48 c7 c6 20 84 f8 8a e8 ca 3a 10 00 0f 0b e8 f3 59 d2 ff <0f> 0b e8 ec 59 d2 ff 4c 89 f7 48 c7 c6 60 86 f8 8a e8 ad 3a 10 00
RSP: 0018:ffffc90000147b88 EFLAGS: 00010246
RAX: ffffffff81b9813d RBX: 0000000000000082 RCX: ffff88813fefba80
RDX: 0000000080000100 RSI: ffffffff8aedcc60 RDI: ffffffff8b4bbfe0
RBP: 1ffffd40000ed426 R08: dffffc0000000000 R09: fffffbfff1d2cabe
R10: fffffbfff1d2cabe R11: 1ffffffff1d2cabd R12: ffffea000076a134
R13: dffffc0000000000 R14: ffffea000076a100 R15: 1ffffd40000ed420
FS: 0000000000000000(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ff727105718 CR3: 00000000291ab000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
---
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-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches
WARNING: multiple messages have this Message-ID (diff)
From: syzbot <syzbot+7e5cf1d80677ec185e63@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, konishi.ryusuke@gmail.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, linux-nilfs@vger.kernel.org,
syzkaller-bugs@googlegroups.com, willy@infradead.org
Subject: [syzbot] [nilfs2?] kernel BUG in folio_end_writeback
Date: Mon, 26 Dec 2022 19:42:34 -0800 [thread overview]
Message-ID: <000000000000dc83d605f0c70a11@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 0a924817d2ed Merge tag '6.2-rc-smb3-client-fixes-part2' of..
git tree: upstream
console+strace: https://syzkaller.appspot.com/x/log.txt?x=16228274480000
kernel config: https://syzkaller.appspot.com/x/.config?x=4e2d7bfa2d6d5a76
dashboard link: https://syzkaller.appspot.com/bug?extid=7e5cf1d80677ec185e63
compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14494888480000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11c189f8480000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/b0959a409a79/disk-0a924817.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/388daa76797b/vmlinux-0a924817.xz
kernel image: https://storage.googleapis.com/syzbot-assets/b9d2d406c075/bzImage-0a924817.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/166e13821ab4/mount_0.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+7e5cf1d80677ec185e63@syzkaller.appspotmail.com
------------[ cut here ]------------
kernel BUG at mm/filemap.c:1615!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 15 Comm: ksoftirqd/0 Not tainted 6.1.0-syzkaller-14321-g0a924817d2ed #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
RIP: 0010:folio_end_writeback+0x34d/0x530 mm/filemap.c:1615
Code: 84 87 00 00 00 e8 13 5a d2 ff e9 36 fd ff ff e8 09 5a d2 ff 4c 89 f7 48 c7 c6 20 84 f8 8a e8 ca 3a 10 00 0f 0b e8 f3 59 d2 ff <0f> 0b e8 ec 59 d2 ff 4c 89 f7 48 c7 c6 60 86 f8 8a e8 ad 3a 10 00
RSP: 0018:ffffc90000147b88 EFLAGS: 00010246
RAX: ffffffff81b9813d RBX: 0000000000000082 RCX: ffff88813fefba80
RDX: 0000000080000100 RSI: ffffffff8aedcc60 RDI: ffffffff8b4bbfe0
RBP: 1ffffd40000ed426 R08: dffffc0000000000 R09: fffffbfff1d2cabe
R10: fffffbfff1d2cabe R11: 1ffffffff1d2cabd R12: ffffea000076a134
R13: dffffc0000000000 R14: ffffea000076a100 R15: 1ffffd40000ed420
FS: 0000000000000000(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ff727105718 CR3: 00000000291ab000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
end_bio_bh_io_sync+0xb1/0x110 fs/buffer.c:2655
req_bio_endio block/blk-mq.c:794 [inline]
blk_update_request+0x51c/0x1040 block/blk-mq.c:926
blk_mq_end_request+0x39/0x70 block/blk-mq.c:1053
blk_complete_reqs block/blk-mq.c:1131 [inline]
blk_done_softirq+0x119/0x160 block/blk-mq.c:1136
__do_softirq+0x277/0x738 kernel/softirq.c:571
run_ksoftirqd+0xa2/0x100 kernel/softirq.c:934
smpboot_thread_fn+0x533/0xa10 kernel/smpboot.c:164
kthread+0x266/0x300 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:folio_end_writeback+0x34d/0x530 mm/filemap.c:1615
Code: 84 87 00 00 00 e8 13 5a d2 ff e9 36 fd ff ff e8 09 5a d2 ff 4c 89 f7 48 c7 c6 20 84 f8 8a e8 ca 3a 10 00 0f 0b e8 f3 59 d2 ff <0f> 0b e8 ec 59 d2 ff 4c 89 f7 48 c7 c6 60 86 f8 8a e8 ad 3a 10 00
RSP: 0018:ffffc90000147b88 EFLAGS: 00010246
RAX: ffffffff81b9813d RBX: 0000000000000082 RCX: ffff88813fefba80
RDX: 0000000080000100 RSI: ffffffff8aedcc60 RDI: ffffffff8b4bbfe0
RBP: 1ffffd40000ed426 R08: dffffc0000000000 R09: fffffbfff1d2cabe
R10: fffffbfff1d2cabe R11: 1ffffffff1d2cabd R12: ffffea000076a134
R13: dffffc0000000000 R14: ffffea000076a100 R15: 1ffffd40000ed420
FS: 0000000000000000(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ff727105718 CR3: 00000000291ab000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
---
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.
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches
next reply other threads:[~2022-12-27 3:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-27 3:42 syzbot [this message]
2022-12-27 3:42 ` [syzbot] [nilfs2?] kernel BUG in folio_end_writeback syzbot
[not found] ` <000000000000dc83d605f0c70a11-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2023-08-20 18:41 ` [syzbot] [nilfs?] " syzbot
2023-08-20 18:41 ` syzbot
2023-08-21 16:47 ` Ryusuke Konishi
2023-08-21 16:47 ` Ryusuke Konishi
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=000000000000dc83d605f0c70a11@google.com \
--to=syzbot+7e5cf1d80677ec185e63-pl5pbv+gp7p466ipttivnc23woclnbcfal8byrjmmd8@public.gmane.org \
--cc=akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org \
--cc=konishi.ryusuke-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org \
--cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=syzkaller-bugs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
--cc=willy-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org \
/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.