[fs?] WARNING in __generic_file_fsync

4 views
Skip to first unread message

syzbot

unread,
Feb 27, 2023, 5:12:39 PM2/27/23
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: a5c95ca18a98 Merge tag 'drm-next-2023-02-23' of git://anon..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14e5f2a8c80000
kernel config: https://syzkaller.appspot.com/x/.config?x=b78226905de65cfe
dashboard link: https://syzkaller.appspot.com/bug?extid=1162ce19c45d08ecdb2e
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
CC: [linux-...@vger.kernel.org linux-...@vger.kernel.org vi...@zeniv.linux.org.uk]

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/436b5c9f9937/disk-a5c95ca1.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/2308b23c5566/vmlinux-a5c95ca1.xz
kernel image: https://storage.googleapis.com/syzbot-assets/156b566b916d/bzImage-a5c95ca1.xz

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

------------[ cut here ]------------
DEBUG_RWSEMS_WARN_ON((rwsem_owner(sem) != current) && !rwsem_test_oflags(sem, RWSEM_NONSPINNABLE)): count = 0x0, magic = 0xffff88803f4d71d0, owner = 0x0, curr 0xffff88801eaf8000, list empty
WARNING: CPU: 0 PID: 6379 at kernel/locking/rwsem.c:1369 __up_write kernel/locking/rwsem.c:1369 [inline]
WARNING: CPU: 0 PID: 6379 at kernel/locking/rwsem.c:1369 up_write+0x425/0x520 kernel/locking/rwsem.c:1626
Modules linked in:
CPU: 0 PID: 6379 Comm: syz-executor.4 Not tainted 6.2.0-syzkaller-08237-ga5c95ca18a98 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/21/2023
RIP: 0010:__up_write kernel/locking/rwsem.c:1369 [inline]
RIP: 0010:up_write+0x425/0x520 kernel/locking/rwsem.c:1626
Code: 3c 02 00 0f 85 da 00 00 00 48 8b 55 00 4d 89 f1 53 4d 89 f8 4c 89 e9 48 c7 c6 20 52 4c 8a 48 c7 c7 60 50 4c 8a e8 8b 96 e7 ff <0f> 0b 59 e9 dd fc ff ff 48 89 df e8 5b c6 71 00 e9 1a fc ff ff 48
RSP: 0018:ffffc900066ffe60 EFLAGS: 00010286
RAX: 0000000000000000 RBX: ffffffff8a4c4fa0 RCX: ffffc9000f042000
RDX: 0000000000040000 RSI: ffffffff814c2c17 RDI: 0000000000000001
RBP: ffff88803f4d71d0 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000001 R11: 0000000000000000 R12: ffff88803f4d71d8
R13: ffff88803f4d71d0 R14: ffff88801eaf8000 R15: 0000000000000000
FS: 00007f01dee40700(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffc3b9c6bf8 CR3: 000000007636a000 CR4: 0000000000350ef0
Call Trace:
<TASK>
inode_unlock include/linux/fs.h:761 [inline]
__generic_file_fsync+0x184/0x1f0 fs/libfs.c:1148
generic_file_fsync+0x77/0x120 fs/libfs.c:1173
vfs_fsync_range fs/sync.c:188 [inline]
vfs_fsync fs/sync.c:202 [inline]
do_fsync fs/sync.c:212 [inline]
__do_sys_fdatasync fs/sync.c:225 [inline]
__se_sys_fdatasync fs/sync.c:223 [inline]
__x64_sys_fdatasync+0xc9/0x140 fs/sync.c:223
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f01de08c0f9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 19 00 00 90 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:00007f01dee40168 EFLAGS: 00000246 ORIG_RAX: 000000000000004b
RAX: ffffffffffffffda RBX: 00007f01de1ac050 RCX: 00007f01de08c0f9
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000005
RBP: 00007f01de0e7ae9 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffd64fbbe2f R14: 00007f01dee40300 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 syzk...@googlegroups.com.

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

syzbot

unread,
May 24, 2023, 6:02:37 PM5/24/23
to syzkaller-upst...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages