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 91F13C433EF for ; Tue, 7 Jun 2022 13:11:24 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 1CC6A6B0073; Tue, 7 Jun 2022 09:11:24 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 154336B0074; Tue, 7 Jun 2022 09:11:24 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id F36876B0075; Tue, 7 Jun 2022 09:11:23 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0016.hostedemail.com [216.40.44.16]) by kanga.kvack.org (Postfix) with ESMTP id DD1E06B0073 for ; Tue, 7 Jun 2022 09:11:23 -0400 (EDT) Received: from smtpin16.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay13.hostedemail.com (Postfix) with ESMTP id 9DBDD60987 for ; Tue, 7 Jun 2022 13:11:23 +0000 (UTC) X-FDA: 79551476046.16.D503198 Received: from mail-io1-f72.google.com (mail-io1-f72.google.com [209.85.166.72]) by imf16.hostedemail.com (Postfix) with ESMTP id EB8AA18004E for ; Tue, 7 Jun 2022 13:11:03 +0000 (UTC) Received: by mail-io1-f72.google.com with SMTP id s145-20020a6b2c97000000b006692e678769so4340166ios.21 for ; Tue, 07 Jun 2022 06:11:22 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:date:message-id:subject:from:to; bh=QdpiH1zf2g1QfmGEmiyd/ASppcMDWZ+/Qd+vKzppL80=; b=62S71lWt5e+HKaEfetZvvhP2hb7Ow0ohSETUnDDJTbYE8GHoRgOIa0KDDkriZ4nvOF jeuP4CFhfC22vckpVDZSwXTwR2ASONLR+7O4AQZqjtm2DoI1JQRcAOurMPWPexYkJNB+ wpF+6LGARDSGLbjFGdTQoD/zqn//4P4yrouv3hILxjLF0kkWOQRziT24XMRTXqhcGVIF PW5YPphTqIjlVe4iyxTnyKxooUs3Z1yR+VbU5OAjShOXYtrx0F+hPRarCqgLgaGzhxI4 gPwtbhlGLRJQ+gwYw1drFza5hNsJ5t0FAu+JXL89eMpkb1n2SdvdnOeEJd8tgizkLEIZ jT/w== X-Gm-Message-State: AOAM533xA1DC1iuHr0FojulDLN8Vu8CwbMx3lVfURvT+Enh6uHZsnuDW 1b03JFegVVoATUaVJOJ21dfArnWokQmBOsUkIqS6k/0K/Cmw X-Google-Smtp-Source: ABdhPJzpsElH7CPkj15sJP83oYbAf5DXGOYbkFiMYnv/JqtbiwHAf5e7dMZADXg1Y8w3A9Y3Zst4XhlgjYmAuvLs1hgPCC51LgTL MIME-Version: 1.0 X-Received: by 2002:a05:6e02:1c26:b0:2d3:bbe3:9223 with SMTP id m6-20020a056e021c2600b002d3bbe39223mr16048928ilh.176.1654607482511; Tue, 07 Jun 2022 06:11:22 -0700 (PDT) Date: Tue, 07 Jun 2022 06:11:22 -0700 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <0000000000003ce9d105e0db53c8@google.com> Subject: [syzbot] KASAN: use-after-free Read in copy_page_from_iter_atomic (2) 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" X-Stat-Signature: xrzwkgqbyu5xhsmt74xrbawu56upt67d Authentication-Results: imf16.hostedemail.com; dkim=none; dmarc=fail reason="SPF not aligned (relaxed), No valid DKIM" header.from=appspotmail.com (policy=none); spf=pass (imf16.hostedemail.com: domain of 3ek6fYgkbAK8hnoZPaaTgPeeXS.VddVaTjhTgRdciTci.Rdb@M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com designates 209.85.166.72 as permitted sender) smtp.mailfrom=3ek6fYgkbAK8hnoZPaaTgPeeXS.VddVaTjhTgRdciTci.Rdb@M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com X-Rspam-User: X-Rspamd-Server: rspam11 X-Rspamd-Queue-Id: EB8AA18004E X-HE-Tag: 1654607463-211381 X-Bogosity: Ham, tests=bogofilter, spamicity=0.001228, 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: 73d0e32571a0 Add linux-next specific files for 20220607 git tree: linux-next console output: https://syzkaller.appspot.com/x/log.txt?x=1433bacff00000 kernel config: https://syzkaller.appspot.com/x/.config?x=448ee2b64e828049 dashboard link: https://syzkaller.appspot.com/bug?extid=d2dd123304b4ae59f1bd 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+d2dd123304b4ae59f1bd@syzkaller.appspotmail.com BTRFS error (device loop2): bad tree block start, want 22036480 have 0 ================================================================== BUG: KASAN: use-after-free in copy_page_from_iter_atomic+0xef6/0x1b30 lib/iov_iter.c:969 Read of size 4096 at addr ffff888177101000 by task kworker/u4:30/4131 CPU: 0 PID: 4131 Comm: kworker/u4:30 Not tainted 5.19.0-rc1-next-20220607-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Workqueue: loop2 loop_workfn Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106 print_address_description.constprop.0.cold+0xeb/0x495 mm/kasan/report.c:313 print_report mm/kasan/report.c:429 [inline] kasan_report.cold+0xf4/0x1c6 mm/kasan/report.c:491 check_region_inline mm/kasan/generic.c:183 [inline] kasan_check_range+0x13d/0x180 mm/kasan/generic.c:189 memcpy+0x20/0x60 mm/kasan/shadow.c:65 copy_page_from_iter_atomic+0xef6/0x1b30 lib/iov_iter.c:969 generic_perform_write+0x2b8/0x560 mm/filemap.c:3734 __generic_file_write_iter+0x2aa/0x4d0 mm/filemap.c:3854 generic_file_write_iter+0xd7/0x220 mm/filemap.c:3886 call_write_iter include/linux/fs.h:2059 [inline] do_iter_readv_writev+0x3d1/0x640 fs/read_write.c:742 do_iter_write+0x182/0x700 fs/read_write.c:868 vfs_iter_write+0x70/0xa0 fs/read_write.c:909 lo_write_bvec drivers/block/loop.c:249 [inline] lo_write_simple drivers/block/loop.c:271 [inline] do_req_filebacked drivers/block/loop.c:495 [inline] loop_handle_cmd drivers/block/loop.c:1859 [inline] loop_process_work+0xd83/0x2050 drivers/block/loop.c:1894 process_one_work+0x996/0x1610 kernel/workqueue.c:2289 worker_thread+0x665/0x1080 kernel/workqueue.c:2436 kthread+0x2e9/0x3a0 kernel/kthread.c:376 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:302 The buggy address belongs to the physical page: page:ffffea0005dc4040 refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x177101 flags: 0x57ff00000000000(node=1|zone=2|lastcpupid=0x7ff) raw: 057ff00000000000 ffffea0005dc4048 ffffea0005dc4048 0000000000000000 raw: 0000000000000000 0000000000000000 00000000ffffffff 0000000000000000 page dumped because: kasan: bad access detected page_owner info is not present (never set?) Memory state around the buggy address: ffff888177100f00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ffff888177100f80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff >ffff888177101000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ^ ffff888177101080: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ffff888177101100: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ================================================================== --- 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.