From: syzbot <syzbot+ecab51a4a5b9f26eeaa1@syzkaller.appspotmail.com>
To: adilger.kernel@dilger.ca, linux-ext4@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
tytso@mit.edu
Subject: [syzbot] WARNING in ext4_dirty_folio
Date: Sat, 26 Mar 2022 08:24:18 -0700 [thread overview]
Message-ID: <0000000000003fb2e905db20ac96@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 34af78c4e616 Merge tag 'iommu-updates-v5.18' of git://git...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=176c1bb3700000
kernel config: https://syzkaller.appspot.com/x/.config?x=6190c85675271e4a
dashboard link: https://syzkaller.appspot.com/bug?extid=ecab51a4a5b9f26eeaa1
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
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+ecab51a4a5b9f26eeaa1@syzkaller.appspotmail.com
------------[ cut here ]------------
WARNING: CPU: 1 PID: 7386 at fs/ext4/inode.c:3600 ext4_dirty_folio+0xf4/0x120 fs/ext4/inode.c:3600
Modules linked in:
CPU: 1 PID: 7386 Comm: syz-executor.1 Tainted: G W 5.17.0-syzkaller-09727-g34af78c4e616 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:ext4_dirty_folio+0xf4/0x120 fs/ext4/inode.c:3600
Code: 1b 31 ff 48 c1 eb 03 83 e3 01 89 de e8 25 c5 5d ff 84 db 0f 85 72 ff ff ff e8 38 c1 5d ff 0f 0b e9 66 ff ff ff e8 2c c1 5d ff <0f> 0b eb 88 48 89 df e8 a0 62 a9 ff e9 3d ff ff ff e8 96 62 a9 ff
RSP: 0018:ffffc90004dc7a48 EFLAGS: 00010246
RAX: 0000000000040000 RBX: 0000000000000001 RCX: ffffc9000c2b5000
RDX: 0000000000040000 RSI: ffffffff821b50c4 RDI: ffffea00018ac0a8
RBP: ffffea00018ac080 R08: 0000000000000000 R09: 0000000000000001
R10: ffffffff821b5021 R11: 0000000000000000 R12: ffff888044c34b10
R13: dffffc0000000000 R14: ffffea00018ac000 R15: ffffea00018ac080
FS: 00007f35859cb700(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000200001c0 CR3: 000000001ceb7000 CR4: 0000000000350ef0
Call Trace:
<TASK>
folio_mark_dirty+0xc1/0x140 mm/page-writeback.c:2632
unpin_user_pages_dirty_lock mm/gup.c:299 [inline]
unpin_user_pages_dirty_lock+0x404/0x4c0 mm/gup.c:263
process_vm_rw_single_vec mm/process_vm_access.c:126 [inline]
process_vm_rw_core.constprop.0+0x7bb/0x990 mm/process_vm_access.c:215
process_vm_rw+0x29c/0x300 mm/process_vm_access.c:283
__do_sys_process_vm_writev mm/process_vm_access.c:303 [inline]
__se_sys_process_vm_writev mm/process_vm_access.c:298 [inline]
__x64_sys_process_vm_writev+0xdf/0x1b0 mm/process_vm_access.c:298
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+0x44/0xae
RIP: 0033:0x7f3584889049
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f35859cb168 EFLAGS: 00000246 ORIG_RAX: 0000000000000137
RAX: ffffffffffffffda RBX: 00007f358499c030 RCX: 00007f3584889049
RDX: 0000000000000001 RSI: 0000000020c22000 RDI: 000000000000012e
RBP: 00007f35848e308d R08: 0000000000000001 R09: 0000000000000000
R10: 0000000020c22fa0 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffeca831cef R14: 00007f35859cb300 R15: 0000000000022000
</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.
next reply other threads:[~2022-03-26 15:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-26 15:24 syzbot [this message]
2022-06-08 11:36 ` [syzbot] WARNING in ext4_dirty_folio syzbot
2023-04-29 21:47 ` Theodore Ts'o
2023-04-29 21:47 ` syzbot
[not found] <20220611043411.1727-1-hdanton@sina.com>
2022-06-11 4:53 ` syzbot
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=0000000000003fb2e905db20ac96@google.com \
--to=syzbot+ecab51a4a5b9f26eeaa1@syzkaller.appspotmail.com \
--cc=adilger.kernel@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tytso@mit.edu \
/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.