From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id DDA3DC4332F for ; Fri, 25 Nov 2022 13:37:45 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 0DB836B0071; Fri, 25 Nov 2022 08:37:45 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id 08C046B0072; Fri, 25 Nov 2022 08:37:45 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id EBC036B0073; Fri, 25 Nov 2022 08:37:44 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0014.hostedemail.com [216.40.44.14]) by kanga.kvack.org (Postfix) with ESMTP id DA1146B0071 for ; Fri, 25 Nov 2022 08:37:44 -0500 (EST) Received: from smtpin21.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay03.hostedemail.com (Postfix) with ESMTP id A3EFDA0BB6 for ; Fri, 25 Nov 2022 13:37:44 +0000 (UTC) X-FDA: 80172067248.21.94531A9 Received: from mail-il1-f200.google.com (mail-il1-f200.google.com [209.85.166.200]) by imf21.hostedemail.com (Postfix) with ESMTP id 25A8A1C000D for ; Fri, 25 Nov 2022 13:37:43 +0000 (UTC) Received: by mail-il1-f200.google.com with SMTP id d19-20020a056e020c1300b00300b5a12c44so2877638ile.15 for ; Fri, 25 Nov 2022 05:37:43 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:from:subject:message-id:date:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=MylCb3p+Ls6myJyGJs1nv54tAD4Nw5G5SgxoxqrICpQ=; b=jEalN2IyMUK9NK1mDa9ncuWE2QZ2r/m+jI0clEjdZqR3FNd6pgHpMFMUS/Bu+FcRW/ te9LChu/s7Vh0mBmiroo1Deuq08sXtgFWZsHLwdG921e9SNJbZuTuefdxX8jqVsOLo0r 1v1PlQ3cRYnZPiwrRC7omJdriO88Qqkw4tdPy6CIBUUEKGgFwNT8WBTwZw6nZxZIjbws iFMzWK3z78Mn5hjNf8mSe3PNfGIalyMHnxmNf2OeNHYy6Ip5fZPEbzsKg9ZAlhU5pjih GggMPIt47WPH2ryf0CAO0fR/qYTj6oWncBoD5t+m7N9INqriDdvtDaTJndeJxTphwIc8 rmgQ== X-Gm-Message-State: ANoB5pkicbpyGeoxAkyAhbDnLk2uSebTO7r8MwO8ktxVVATogH/P9y3m huoJBPrAPg9uhvoyUtYkU+wV7eWJHF2vRQtxSP9yvFq4sNFW X-Google-Smtp-Source: AA0mqf5sxHXLzFtKueDQg2b5fadddVGPga7WERR+IPad9WPKkIILVUC6WdR5P06FlOc0vfVE+YDnO1HPRp3QWtQFH3dhVORgZcYg MIME-Version: 1.0 X-Received: by 2002:a05:6e02:f52:b0:302:b44f:a09 with SMTP id y18-20020a056e020f5200b00302b44f0a09mr10193988ilj.227.1669383463212; Fri, 25 Nov 2022 05:37:43 -0800 (PST) Date: Fri, 25 Nov 2022 05:37:43 -0800 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <000000000000519d0205ee4ba094@google.com> Subject: [syzbot] WARNING in iov_iter_revert (3) From: syzbot To: akpm@linux-foundation.org, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, syzkaller-bugs@googlegroups.com, willy@infradead.org Content-Type: text/plain; charset="UTF-8" ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1669383464; a=rsa-sha256; cv=none; b=I5aqGDd4Zd/J41sKi4YQ/HA9T6G+Aa03JBOkec3N/8vvKmr1DV5xp1e7LwPRchGB4Jabti 7BojkQNtVzPlv4DTvAEQV44gjf7gEyzpxTJHtsCeS2ZzJXMsRVA9Rk3V678fFCZTgOftaS VfjDN7wjioG1ee3DbxOjL31Nzr0dXUU= ARC-Authentication-Results: i=1; imf21.hostedemail.com; dkim=none; spf=pass (imf21.hostedemail.com: domain of 3J8WAYwkbANYKQRC2DD6J2HHA5.8GG8D6MK6J4GFL6FL.4GE@M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com designates 209.85.166.200 as permitted sender) smtp.mailfrom=3J8WAYwkbANYKQRC2DD6J2HHA5.8GG8D6MK6J4GFL6FL.4GE@M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com; dmarc=fail reason="SPF not aligned (relaxed), No valid DKIM" header.from=appspotmail.com (policy=none) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1669383464; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type:content-transfer-encoding:in-reply-to: references; bh=MylCb3p+Ls6myJyGJs1nv54tAD4Nw5G5SgxoxqrICpQ=; b=O7JDn4iqJhLevR6BoWKspyZ/DcrQ1Si6yq6S35kN7o2KJgyeA6TdxDkAqTer+GEoLy2ACl J4uMt6g3RYWJTLL1jEh636/Z3VWiGv3e8jWjgi6YJxbcjOBtRddMWF+qZDY+rzBAfq1FT8 9JLgQiqqavd6Q0WIIWzoZY9nduT6MWM= X-Stat-Signature: sspcz7g6o4gfr459bcxfnqmrpo7u47dp X-Rspamd-Queue-Id: 25A8A1C000D X-Rspam-User: Authentication-Results: imf21.hostedemail.com; dkim=none; spf=pass (imf21.hostedemail.com: domain of 3J8WAYwkbANYKQRC2DD6J2HHA5.8GG8D6MK6J4GFL6FL.4GE@M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com designates 209.85.166.200 as permitted sender) smtp.mailfrom=3J8WAYwkbANYKQRC2DD6J2HHA5.8GG8D6MK6J4GFL6FL.4GE@M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com; dmarc=fail reason="SPF not aligned (relaxed), No valid DKIM" header.from=appspotmail.com (policy=none) X-Rspamd-Server: rspam10 X-HE-Tag: 1669383463-959057 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: Hello, syzbot found the following issue on: HEAD commit: eb7081409f94 Linux 6.1-rc6 git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=105ff881880000 kernel config: https://syzkaller.appspot.com/x/.config?x=8cdf448d3b35234 dashboard link: https://syzkaller.appspot.com/bug?extid=8c7a4ca1cc31b7ce7070 compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2 Unfortunately, I don't have any reproducer for this issue yet. Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/4a019f55c517/disk-eb708140.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/eb36e890aa8b/vmlinux-eb708140.xz kernel image: https://storage.googleapis.com/syzbot-assets/feee2c23ec64/bzImage-eb708140.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+8c7a4ca1cc31b7ce7070@syzkaller.appspotmail.com ------------[ cut here ]------------ WARNING: CPU: 0 PID: 7897 at lib/iov_iter.c:918 iov_iter_revert+0x394/0x850 Modules linked in: CPU: 0 PID: 7897 Comm: syz-executor.2 Not tainted 6.1.0-rc6-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022 RIP: 0010:iov_iter_revert+0x394/0x850 lib/iov_iter.c:918 Code: 80 3c 01 00 48 8b 5c 24 20 74 08 48 89 df e8 e3 c9 a3 fd 4c 89 2b 48 83 c4 68 5b 41 5c 41 5d 41 5e 41 5f 5d c3 e8 5c b1 4f fd <0f> 0b eb e8 48 8d 6b 18 48 89 e8 48 c1 e8 03 42 80 3c 28 00 74 08 RSP: 0018:ffffc90015fe7ac8 EFLAGS: 00010287 RAX: ffffffff843ae714 RBX: ffffc90015fe7e40 RCX: 0000000000040000 RDX: ffffc9000c1cc000 RSI: 000000000003ef70 RDI: 000000000003ef71 RBP: fffffffffff80e18 R08: ffffffff843ae3bc R09: fffffbfff1d2f2de R10: fffffbfff1d2f2de R11: 1ffffffff1d2f2dd R12: fffffffffff80e18 R13: ffffc90015fe7e40 R14: ffffc90015fe7e50 R15: 000000007fefef0c FS: 00007f212fd7e700(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 000000c00c59ffb8 CR3: 000000007dc32000 CR4: 00000000003506f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: generic_file_read_iter+0x3d4/0x540 mm/filemap.c:2804 do_iter_read+0x6e3/0xc10 fs/read_write.c:796 vfs_readv fs/read_write.c:916 [inline] do_preadv+0x1f4/0x330 fs/read_write.c:1008 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x7f212f08b639 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:00007f212fd7e168 EFLAGS: 00000246 ORIG_RAX: 0000000000000147 RAX: ffffffffffffffda RBX: 00007f212f1ac1f0 RCX: 00007f212f08b639 RDX: 0000000000000001 RSI: 0000000020000100 RDI: 0000000000000003 RBP: 00007f212f0e6ae9 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007ffdc886837f R14: 00007f212fd7e300 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@googlegroups.com. syzbot will keep track of this issue. See: https://goo.gl/tpsmEJ#status for how to communicate with syzbot.