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 69F17C7EE24 for ; Sat, 3 Jun 2023 06:20:49 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231621AbjFCGUq (ORCPT ); Sat, 3 Jun 2023 02:20:46 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:35600 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229523AbjFCGUm (ORCPT ); Sat, 3 Jun 2023 02:20:42 -0400 Received: from szxga02-in.huawei.com (szxga02-in.huawei.com [45.249.212.188]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 41C9DE58; Fri, 2 Jun 2023 23:20:40 -0700 (PDT) Received: from dggpeml500021.china.huawei.com (unknown [172.30.72.56]) by szxga02-in.huawei.com (SkyGuard) with ESMTP id 4QY8qn0xkpzTkkG; Sat, 3 Jun 2023 14:20:21 +0800 (CST) Received: from [10.174.177.174] (10.174.177.174) by dggpeml500021.china.huawei.com (7.185.36.21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.23; Sat, 3 Jun 2023 14:20:35 +0800 Message-ID: Date: Sat, 3 Jun 2023 14:20:34 +0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.1.2 Subject: Re: [syzbot] Monthly ext4 report (May 2023) Content-Language: en-US To: Theodore Ts'o CC: syzbot , , , , , , yangerkun , Baokun Li References: <000000000000834af205fce87c00@google.com> <20230602210639.GA1154817@mit.edu> <20230603043028.GE1128875@mit.edu> From: Baokun Li In-Reply-To: <20230603043028.GE1128875@mit.edu> Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: [10.174.177.174] X-ClientProxiedBy: dggems706-chm.china.huawei.com (10.3.19.183) To dggpeml500021.china.huawei.com (7.185.36.21) X-CFilter-Loop: Reflected Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2023/6/3 12:30, Theodore Ts'o wrote: > On Sat, Jun 03, 2023 at 10:05:44AM +0800, Baokun Li wrote: >> There are many sources of syzkaller issues, and the patches I send out >> to fix syzkaller issues add Reported-by to all but the ones that fix issues >> reported by our internal syzbot. >> However, there may be multiple syzbot reports for the same issue. > Yes, that happens a lot especially for Lockdep reports; depending on > how the reproducer triggers the locks in which order, there can often > be multiple different lockdep signatures, and Syzkaller can't tell > that they are all the same thing. > > I tend to focus on syzbot reproducers on the upstream Linux instance, > rather than the Android-5.15 syzkaller instance. And that allows me > to use the ext4 subsystem dashboard available at: > > https://syzkaller.appspot.com/upstream/s/ext4 > > It's against this list of reports that the Monthly ext4 report is > generated. So if people who are submitting fixes against syzkaller > reports, it would be nice if they were to check the ext4 dashboard > above to look for syzbot reports that might be also relevant to your > patch. > > Thanks, > > - Ted > OK, later to fix any ext4 issue, I will check if the issue is in the ext4 subsystem dashboard. Thanks! -- With Best Regards, Baokun Li .