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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 7DFFEC7EE21 for ; Thu, 4 May 2023 12:08:11 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230353AbjEDMIK (ORCPT ); Thu, 4 May 2023 08:08:10 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:43234 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229828AbjEDMII (ORCPT ); Thu, 4 May 2023 08:08:08 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id C6C745FCF for ; Thu, 4 May 2023 05:08:06 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 629C8614D3 for ; Thu, 4 May 2023 12:08:06 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 71B27C433EF; Thu, 4 May 2023 12:08:03 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1683202085; bh=c5fHNZL9gOzBsNhK0yGMsJoyKVL5D1e08PMrRpEg6W4=; h=Date:Subject:To:References:From:In-Reply-To:From; b=VMm0aaiaP/f6HZUlefG+lLRiWMw8jAWz5osg6aTLPdj4RWj4fgrfXmt0B1OFRyY6D jbN3lgI2Hs24f419n3Fo1fLuj4k4hSqo/l5FLaGPLMPcNaAJ8qTyJPGWW26s5W9+cF R3nOi0seg2jolpgfKtCVj3NW5K5CiGgFXez6bE/MNRh0JxLtQtE/ziqtLiGT1l0zLY vb2wsXJK0VSAx8RkbDaRR6Kahv8o7SQvf1UnfJKPbjxBa0xurNOIA3g7JaJfNyiF3m zttRSHkFDEsDtH3HjCCNJblN3P6lBV8bVVooreCYN76ESKUqB4rozUUxdDRrkO/2f8 poLDeLG4sD7eg== Message-ID: Date: Thu, 4 May 2023 20:08:00 +0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.10.1 Subject: Re: [syzbot] [f2fs?] WARNING: lock held when returning to user space in f2fs_write_single_data_page Content-Language: en-US To: syzbot , jaegeuk@kernel.org, linux-f2fs-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com References: <0000000000000534da05faa4d3d4@google.com> From: Chao Yu In-Reply-To: <0000000000000534da05faa4d3d4@google.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2023/5/2 1:05, syzbot wrote: > Hello, > > syzbot found the following issue on: > > HEAD commit: 58390c8ce1bd Merge tag 'iommu-updates-v6.4' of git://git.k.. > git tree: upstream > console+strace: https://syzkaller.appspot.com/x/log.txt?x=136e6ef8280000 > kernel config: https://syzkaller.appspot.com/x/.config?x=5eadbf0d3c2ece89 > dashboard link: https://syzkaller.appspot.com/bug?extid=eb6201248f684e99b9f8 > compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2 > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16bbb03c280000 > C reproducer: https://syzkaller.appspot.com/x/repro.c?x=140d36f8280000 > > Downloadable assets: > disk image: https://storage.googleapis.com/syzbot-assets/60130779f509/disk-58390c8c.raw.xz > vmlinux: https://storage.googleapis.com/syzbot-assets/d7f0cdd29b71/vmlinux-58390c8c.xz > kernel image: https://storage.googleapis.com/syzbot-assets/de415ad52ae4/bzImage-58390c8c.xz > mounted in repro: https://storage.googleapis.com/syzbot-assets/dc89d01cd6e9/mount_0.gz > > IMPORTANT: if you fix the issue, please add the following tag to the commit: > Reported-by: syzbot+eb6201248f684e99b9f8@syzkaller.appspotmail.com #syz test https://git.kernel.org/pub/scm/linux/kernel/git/chao/linux.git dev-test > > syz-executor768: attempt to access beyond end of device > loop0: rw=2049, sector=77824, nr_sectors = 2048 limit=63271 > syz-executor768: attempt to access beyond end of device > loop0: rw=2049, sector=79872, nr_sectors = 2048 limit=63271 > ================================================ > WARNING: lock held when returning to user space! > 6.3.0-syzkaller-12049-g58390c8ce1bd #0 Not tainted > ------------------------------------------------ > syz-executor768/4998 is leaving the kernel with locks still held! > 1 lock held by syz-executor768/4998: > #0: ffff88807e800448 (&sbi->node_write){++++}-{3:3}, at: f2fs_down_read fs/f2fs/f2fs.h:2087 [inline] > #0: ffff88807e800448 (&sbi->node_write){++++}-{3:3}, at: f2fs_write_single_data_page+0xa10/0x1d50 fs/f2fs/data.c:2842 > > > --- > 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. > > If the bug is already fixed, let syzbot know by replying with: > #syz fix: exact-commit-title > > If you want syzbot to run the reproducer, reply with: > #syz test: git://repo/address.git branch-or-commit-hash > If you attach or paste a git patch, syzbot will apply it before testing. > > If you want to change bug's subsystems, reply with: > #syz set subsystems: new-subsystem > (See the list of subsystem names on the web dashboard) > > If the bug is a duplicate of another bug, reply with: > #syz dup: exact-subject-of-another-report > > If you want to undo deduplication, reply with: > #syz undup