lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <000000000000f3ee6005c8c45628@google.com>
Date:   Wed, 04 Aug 2021 16:41:21 -0700
From:   syzbot <syzbot+7e3ea7eaebc6168ab4d5@...kaller.appspotmail.com>
To:     linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
        syzkaller-bugs@...glegroups.com, viro@...iv.linux.org.uk
Subject: [syzbot] WARNING in iov_iter_pipe (2)

Hello,

syzbot found the following issue on:

HEAD commit:    d5ad8ec3cfb5 Merge tag 'media/v5.14-2' of git://git.kernel..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=156d81ae300000
kernel config:  https://syzkaller.appspot.com/x/.config?x=343fd21f6f4da2d6
dashboard link: https://syzkaller.appspot.com/bug?extid=7e3ea7eaebc6168ab4d5
compiler:       gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.1

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+7e3ea7eaebc6168ab4d5@...kaller.appspotmail.com

------------[ cut here ]------------
WARNING: CPU: 0 PID: 31934 at lib/iov_iter.c:1158 iov_iter_pipe+0x228/0x2d0 lib/iov_iter.c:1158
Modules linked in:
CPU: 0 PID: 31934 Comm: syz-executor.2 Not tainted 5.14.0-rc4-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:iov_iter_pipe+0x228/0x2d0 lib/iov_iter.c:1158
Code: 83 c0 03 38 d0 7c 04 84 d2 75 54 44 89 63 24 48 83 c4 10 5b 5d 41 5c 41 5d 41 5e 41 5f c3 e8 5f 6f a1 fd 0f 0b e8 58 6f a1 fd <0f> 0b 48 b8 00 00 00 00 00 fc ff df 48 8b 14 24 48 c1 ea 03 0f b6
RSP: 0018:ffffc90001c9f9e0 EFLAGS: 00010246
RAX: 0000000000040000 RBX: ffffc90001c9fa60 RCX: ffffc90003359000
RDX: 0000000000040000 RSI: ffffffff83d42c08 RDI: 0000000000000003
RBP: ffff88807eb65400 R08: 0000000000000010 R09: 0000000000008000
R10: ffffffff83d42aca R11: 0000000000004000 R12: 0000000000000050
R13: 0000000000000000 R14: 0000000000000010 R15: 0000000000000010
FS:  00007f0929a3d700(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b2f548000 CR3: 000000007e97f000 CR4: 0000000000350ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000600
Call Trace:
 generic_file_splice_read+0x9c/0x6c0 fs/splice.c:307
 do_splice_to+0x1bf/0x250 fs/splice.c:796
 splice_direct_to_actor+0x2c2/0x8c0 fs/splice.c:870
 do_splice_direct+0x1b3/0x280 fs/splice.c:979
 do_sendfile+0x9f0/0x1120 fs/read_write.c:1260
 __do_sys_sendfile64 fs/read_write.c:1325 [inline]
 __se_sys_sendfile64 fs/read_write.c:1311 [inline]
 __x64_sys_sendfile64+0x1cc/0x210 fs/read_write.c:1311
 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:0x4665e9
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 bc ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f0929a3d188 EFLAGS: 00000246 ORIG_RAX: 0000000000000028
RAX: ffffffffffffffda RBX: 000000000056c038 RCX: 00000000004665e9
RDX: 0000000000000000 RSI: 0000000000000006 RDI: 0000000000000008
RBP: 00000000004bfcc4 R08: 0000000000000000 R09: 0000000000000000
R10: 0000800100020001 R11: 0000000000000246 R12: 000000000056c038
R13: 00007ffc9a3f6d4f R14: 00007f0929a3d300 R15: 0000000000022000


---
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@...glegroups.com.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ