From: syzbot <syzbot+5ea720fb6b767fbcab6d@syzkaller.appspotmail.com>
To: djwong@kernel.org, hch@infradead.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-xfs@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: [syzbot] WARNING in iomap_page_release
Date: Tue, 13 Jul 2021 14:21:29 -0700 [thread overview]
Message-ID: <00000000000044ed0305c707d219@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 92510a7f Add linux-next specific files for 20210709
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=14fa5bc4300000
kernel config: https://syzkaller.appspot.com/x/.config?x=505de2716f052686
dashboard link: https://syzkaller.appspot.com/bug?extid=5ea720fb6b767fbcab6d
Unfortunately, I don't have any reproducer for this issue yet.
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+5ea720fb6b767fbcab6d@syzkaller.appspotmail.com
------------[ cut here ]------------
WARNING: CPU: 0 PID: 8462 at fs/iomap/buffered-io.c:77 iomap_page_release+0x687/0x790 fs/iomap/buffered-io.c:77
Modules linked in:
CPU: 1 PID: 8462 Comm: syz-executor.1 Tainted: G W 5.13.0-next-20210709-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:iomap_page_release+0x687/0x790 fs/iomap/buffered-io.c:77
Code: 4f 8d 8a ff 49 8d 6d ff e9 1b fe ff ff e8 41 8d 8a ff 0f 0b e9 71 fe ff ff e8 35 8d 8a ff 0f 0b e9 97 fd ff ff e8 29 8d 8a ff <0f> 0b e9 32 fd ff ff 4c 89 ef e8 3a 9a d0 ff e9 96 f9 ff ff 48 89
RSP: 0018:ffffc9000169f830 EFLAGS: 00010293
RAX: 0000000000000000 RBX: 0000000000001000 RCX: 0000000000000000
RDX: ffff8880265f8000 RSI: ffffffff81eb0f77 RDI: 0000000000000003
RBP: ffffea0001380bc0 R08: 0000000000000000 R09: ffff88808995165b
R10: ffffffff81eb0ca7 R11: 000000000000003f R12: ffff888089951658
R13: ffffea0001380bc8 R14: 000000000000000c R15: 0000000000000031
FS: 00000000027d1400(0000) GS:ffff8880b9d00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000544038 CR3: 00000000702a5000 CR4: 00000000001506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
iomap_invalidatepage fs/iomap/buffered-io.c:489 [inline]
iomap_invalidatepage+0x46d/0x670 fs/iomap/buffered-io.c:478
do_invalidatepage mm/truncate.c:167 [inline]
truncate_cleanup_page+0x393/0x560 mm/truncate.c:186
truncate_inode_pages_range+0x26c/0x1030 mm/truncate.c:335
gfs2_evict_inode+0x1e1/0x1ff0 fs/gfs2/super.c:1467
evict+0x2ed/0x6b0 fs/inode.c:590
iput_final fs/inode.c:1670 [inline]
iput.part.0+0x539/0x850 fs/inode.c:1696
iput+0x58/0x70 fs/inode.c:1686
gfs2_put_super+0x29a/0x650 fs/gfs2/super.c:668
generic_shutdown_super+0x14c/0x370 fs/super.c:465
kill_block_super+0x97/0xf0 fs/super.c:1395
gfs2_kill_sb+0x104/0x160 fs/gfs2/ops_fstype.c:1682
deactivate_locked_super+0x94/0x160 fs/super.c:335
deactivate_super+0xad/0xd0 fs/super.c:366
cleanup_mnt+0x3a2/0x540 fs/namespace.c:1136
task_work_run+0xdd/0x1a0 kernel/task_work.c:164
tracehook_notify_resume include/linux/tracehook.h:189 [inline]
exit_to_user_mode_loop kernel/entry/common.c:175 [inline]
exit_to_user_mode_prepare+0x27e/0x290 kernel/entry/common.c:209
__syscall_exit_to_user_mode_work kernel/entry/common.c:291 [inline]
syscall_exit_to_user_mode+0x19/0x60 kernel/entry/common.c:302
do_syscall_64+0x42/0xb0 arch/x86/entry/common.c:86
entry_SYSCALL_64_after_hwframe+0x44/0xae
RIP: 0033:0x467a37
Code: ff d0 48 89 c7 b8 3c 00 00 00 0f 05 48 c7 c1 bc ff ff ff f7 d8 64 89 01 48 83 c8 ff c3 66 0f 1f 44 00 00 b8 a6 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 bc ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffeb202ad98 EFLAGS: 00000246
ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000467a37
RDX: 00007ffeb202ae6b RSI: 0000000000000002 RDI: 00007ffeb202ae60
RBP: 00007ffeb202ae60 R08: 00000000ffffffff R09: 00007ffeb202ac30
R10: 00000000027d28e3 R11: 0000000000000246 R12: 00000000004bee70
R13: 00007ffeb202bf30 R14: 00000000027d2810 R15: 00007ffeb202bf70
---
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.
reply other threads:[~2021-07-13 21:21 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=00000000000044ed0305c707d219@google.com \
--to=syzbot+5ea720fb6b767fbcab6d@syzkaller.appspotmail.com \
--cc=djwong@kernel.org \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@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.