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 04894C3DA7A for ; Mon, 2 Jan 2023 05:28:36 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 0CBED8E0002; Mon, 2 Jan 2023 00:28:36 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id 07C0F8E0001; Mon, 2 Jan 2023 00:28:36 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id E85B28E0002; Mon, 2 Jan 2023 00:28:35 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0011.hostedemail.com [216.40.44.11]) by kanga.kvack.org (Postfix) with ESMTP id D4DF88E0001 for ; Mon, 2 Jan 2023 00:28:35 -0500 (EST) Received: from smtpin07.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay06.hostedemail.com (Postfix) with ESMTP id 7B849AAA1B for ; Mon, 2 Jan 2023 05:28:35 +0000 (UTC) X-FDA: 80308728990.07.68DA19C Received: from www262.sakura.ne.jp (www262.sakura.ne.jp [202.181.97.72]) by imf02.hostedemail.com (Postfix) with ESMTP id 384688000E for ; Mon, 2 Jan 2023 05:28:32 +0000 (UTC) Authentication-Results: imf02.hostedemail.com; dkim=none; dmarc=none; spf=none (imf02.hostedemail.com: domain of penguin-kernel@I-love.SAKURA.ne.jp has no SPF policy when checking 202.181.97.72) smtp.mailfrom=penguin-kernel@I-love.SAKURA.ne.jp ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1672637313; a=rsa-sha256; cv=none; b=UxWq6PwBL4U1FeA9go4zaEPfX5wgcG6ruVjFb8Gd2PCcrUWdhkKBV/DxU0YpgbYKEDI28z LMinxzIXL01HJSJvhgk4KtIAb2vc/7BtlIEReVnSQ2n5eBpSUOh3qM0gkQrRxB7rimbXmo QhTWEr1QbzCkRr3jEwkhXvv+AxffVh0= ARC-Authentication-Results: i=1; imf02.hostedemail.com; dkim=none; dmarc=none; spf=none (imf02.hostedemail.com: domain of penguin-kernel@I-love.SAKURA.ne.jp has no SPF policy when checking 202.181.97.72) smtp.mailfrom=penguin-kernel@I-love.SAKURA.ne.jp ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1672637313; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=jEuF1Knnw11jGbD3R6RpGOvVPzCWOPEVS/JcEG3m9ik=; b=HcpBq/UMgsVTadOiqfvNjevu1F8iXGUHu6EpvOADZqflCNyKPiX4L61nYwT3Kqb1oApcfX rcwYlVo3uAhSsjWIdfYb1BXez6/n0nVixENjbhfPrsAqQpGduhNx38zTVfSWgyk3z/PJhG JIN8G2mxnBvkEOWAVIHXFXRN+S6ZyvY= Received: from fsav313.sakura.ne.jp (fsav313.sakura.ne.jp [153.120.85.144]) by www262.sakura.ne.jp (8.15.2/8.15.2) with ESMTP id 3025S9vP091847; Mon, 2 Jan 2023 14:28:09 +0900 (JST) (envelope-from penguin-kernel@I-love.SAKURA.ne.jp) Received: from www262.sakura.ne.jp (202.181.97.72) by fsav313.sakura.ne.jp (F-Secure/fsigk_smtp/550/fsav313.sakura.ne.jp); Mon, 02 Jan 2023 14:28:09 +0900 (JST) X-Virus-Status: clean(F-Secure/fsigk_smtp/550/fsav313.sakura.ne.jp) Received: from [192.168.1.20] (M106072142033.v4.enabler.ne.jp [106.72.142.33]) (authenticated bits=0) by www262.sakura.ne.jp (8.15.2/8.15.2) with ESMTPSA id 3025RkdM091776 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=NO); Mon, 2 Jan 2023 14:28:09 +0900 (JST) (envelope-from penguin-kernel@I-love.SAKURA.ne.jp) Message-ID: <339a74c5-b2d5-1f89-180c-a9d93461ae02@I-love.SAKURA.ne.jp> Date: Mon, 2 Jan 2023 14:27:46 +0900 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.6.1 Subject: Re: [syzbot] [ntfs3?] INFO: task hung in do_user_addr_fault (3) To: Hillf Danton , Linus Torvalds Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org, Waiman Long , Matthew Wilcox , syzkaller-bugs@googlegroups.com, syzbot References: <20230102005409.3474-1-hdanton@sina.com> Content-Language: en-US From: Tetsuo Handa In-Reply-To: <20230102005409.3474-1-hdanton@sina.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Rspam-User: X-Rspamd-Server: rspam03 X-Rspamd-Queue-Id: 384688000E X-Stat-Signature: b5g4kme93ejpbbc1gz5dhuxxqpwtmqnj X-HE-Tag: 1672637312-893866 X-HE-Meta: U2FsdGVkX18inYNN+TAClbw/5xHSiKI0C3v5ixqM+r9ns433oJIiZxmTSs6P+vQwu4WFWqOEYyqyyac1yDzyx9OfpuoyBwre9j7abMdj2sIZTOEwPVasreoDuXad2yxizvzEXudoIZRTo4TtO7/ZZBh0bORlLG5h3jIZvi/vBTmEE+T7FwoiEDysw/QA/YO+/QI1ucWJ+EWUaBtrtIWKwCEGOTzOF23koEXtxb1v4SpWmXUISnl1mOokwa92XK8WQI2lmfL00F5g2hma7OVfaK3YJBX69Kerb/ENCQ/qc0lVLgEhd2iPqEwdMAVhHtSOnOzRz4AqcBwmCLZGteTvNQ1k2ulgXtVDoppFkNDsm3cm6kyPsot2vVSa7zs1Yv28Qgs5RS0kO4v2nXDFBPVIJBa4Re9Ng/k3GzAE5FgqnC0DHWAstVIWdsspm9q31AoUuKqhPsNNgW0rwWOaThjllCMRzCyuptxR7C5hpesc2qd1HAV1eP1IHSYnBIOUR1sCT85s2pTRgDiTQnGcChkbJeeQzBFZiUI5NmRV9wi6hESRcN1+Weifcwi8bJve2v6t09hsolotEs6kQGW16qrgGPAk6BO/o38ED1qN6hBMtDUIDBMm0YAx359xQ6coybENF91ezkwGsW5k8gE7W5GZALkVUA4CtrxK2YcXolX/rcf91retvnjOv6o5k/IhBxbYoH7rvqwxuPbbtOHXfAjNELO3nt8kg5uVOPGpgl4yXI1v4ARJZLDKQSFinxZOTrxwvVp2Bb5lvQwMW/0c6WgPJ0N3nsd1sULUmLS+msor2bwawHumUcJk4d9AuC91baPWlD6PqasjlPKbEioZeCvaB38Q1Edd+L359AlIG6/f84Qv5ruY3orXLab4TXeaZ6D8Sn4o9/uORwUmVw1PLRjDqM35IAfP3s+DLjAfDYDUMEQ6HMy/sJdFpVsxXCOsdlyg0JNCHYDJX9LjHYVdfcQ HitrepOj mnra7AmciKKZ3cz0NV/QZUy+OsIg8IQ6tVPqTuct8AJVGdFbGmbkXyFztlmYLPLB+bYJWv1KSXB88gpE= X-Bogosity: Ham, tests=bogofilter, spamicity=0.000005, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On 2023/01/02 9:54, Hillf Danton wrote: > Even though folio lock is printed in the call trace of syz-executor394/5222 > > folio_lock include/linux/pagemap.h:938 [inline] > > no lockdep radar exists for it in the sake of lock, which makes it harder > than expected or impossible to find the cause of task hung reported. Two sets of same pattern. #0: ffff88801ee04460 (sb_writers#9){.+.+}-{0:0}, at: do_sendfile+0x61c/0xfd0 fs/read_write.c:1254 #1: ffff888073930ca0 (mapping.invalidate_lock#3){.+.+}-{3:3}, at: filemap_update_page+0x72/0x550 mm/filemap.c:2478 #2: ffff888073930860 (&ni->ni_lock/4){+.+.}-{3:3}, at: attr_data_get_block+0x4a6/0x2e40 fs/ntfs3/attrib.c:919 #0: ffff88802c7bc758 (&mm->mmap_lock){++++}-{3:3}, at: vm_mmap_pgoff+0x18f/0x2f0 mm/util.c:518 #1: ffff888073930860 (&ni->ni_lock/4){+.+.}-{3:3}, at: attr_data_get_block+0x4a6/0x2e40 fs/ntfs3/attrib.c:919 #0: ffff88801ee04460 (sb_writers#9){.+.+}-{0:0}, at: mnt_want_write+0x3b/0x80 fs/namespace.c:508 #1: ffff888073930b00 (&sb->s_type->i_mutex_key#14){+.+.}-{3:3}, at: do_truncate+0x205/0x300 fs/open.c:63 #2: ffff888073930860 (&ni->ni_lock/4){+.+.}-{3:3}, at: ntfs3_setattr+0x596/0xca0 fs/ntfs3/file.c:696 #0: ffff888021b06460 (sb_writers#9){.+.+}-{0:0}, at: do_sendfile+0x61c/0xfd0 fs/read_write.c:1254 #1: ffff888075aec7a0 (mapping.invalidate_lock#3){.+.+}-{3:3}, at: filemap_update_page+0x72/0x550 mm/filemap.c:2478 #2: ffff888075aec360 (&ni->ni_lock/4){+.+.}-{3:3}, at: attr_data_get_block+0x4a6/0x2e40 fs/ntfs3/attrib.c:919 #0: ffff888018eead18 (&mm->mmap_lock){++++}-{3:3}, at: vm_mmap_pgoff+0x18f/0x2f0 mm/util.c:518 #1: ffff888075aec360 (&ni->ni_lock/4){+.+.}-{3:3}, at: attr_data_get_block+0x4a6/0x2e40 fs/ntfs3/attrib.c:919 #0: ffff888021b06460 (sb_writers#9){.+.+}-{0:0}, at: mnt_want_write+0x3b/0x80 fs/namespace.c:508 #1: ffff888075aec600 (&sb->s_type->i_mutex_key#14){+.+.}-{3:3}, at: do_truncate+0x205/0x300 fs/open.c:63 #2: ffff888075aec360 (&ni->ni_lock/4){+.+.}-{3:3}, at: ntfs3_setattr+0x596/0xca0 fs/ntfs3/file.c:696 But no hint for syz-executor394/8253. >> 4 locks held by syz-executor394/8253: I'd like to know what does 8253 is doing with what locks held. https://lkml.kernel.org/r/c8893402-d1b2-9fad-3aad-d130c5f5923b@I-love.SAKURA.ne.jp should help, but still no response from Peter nor Ingo. Since this patch has an Ack from Waiman Long, may I send this patch to linux.git via my tree?