Received: by 2002:a05:6359:c8b:b0:c7:702f:21d4 with SMTP id go11csp1074321rwb; Fri, 23 Sep 2022 07:56:35 -0700 (PDT) X-Google-Smtp-Source: AMsMyM690+qLVJQFgwLF1g2fs7iW7Om+gYiypUmr8LcCzmy+uvyQW0RQDCxaonHYPonKSKEQb+nH X-Received: by 2002:a05:6402:1a4d:b0:44e:221d:d1dd with SMTP id bf13-20020a0564021a4d00b0044e221dd1ddmr8994261edb.267.1663944995423; Fri, 23 Sep 2022 07:56:35 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1663944995; cv=none; d=google.com; s=arc-20160816; b=qrMg8z9o3ATdvDpbP1jbLREicdylkl9Tx7T0gSNWOKNxYCNwsdLQF8SMoWV2H8GvIO OH/VPtBh3Ci2EIJfZaAyA0mXQmyOKfNPaIB0Vc2Z6mRbJOBdwpzzbE0iOOMXADFBod/m bWwdII6EuFjaXIZODwAaHdH1RSrmYqmYtbBKUiscwxd/B6Jikz9AW2xBDcq6iBGOZ6+u bsR8ElODCS9vbpjkUQ7SPgA07j8D6VfedP7R61M45T8i45j8aY+317vtJu0ZnIQ6Okks 6q641SsgU+V3w2N3r4Do+rV3VGc3bhZGDB2NxrdelH+jS7Oh4c7upBH9NyvxJnFFworm 5YlQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:from :references:cc:to:content-language:subject:user-agent:mime-version :date:message-id; bh=GT5O46GyYDbX7Bxz3ImS9vvHVkSQ69rSyfUhnTyhFsQ=; b=rQQRvOi70PhkmVeaKL7u2XtIJp69tJZR+qR78fvjtza++6C4yD0Mdk4mkdjek7Ja2w 3RLdIkA2MyaoHVMbl2GIBthOadzrfIDsTxfMJKRVAVXqtOckbIaBtUP4wuPTzem1GqyX RFKVDD+6CIlvmRrD7gowpLlx16tO6aknrN4OPKxu75AUyDj4fAjY5BMjVArFXAhLnsn8 RhtNHiMVl3vBnUicbL/yeDfBQPEKgepGrZErTaiIjWcXjYyC8270XWRf3E26vI7rSVqB rVDMKExTXwGg/DTPT+0v199/eVFnabwXV8IPoD2lroVVhXIrtNb84ylYkQLXoxU/axTb eYdw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id u9-20020a50a409000000b0045114a45852si8041898edb.536.2022.09.23.07.56.09; Fri, 23 Sep 2022 07:56:35 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230282AbiIWOft (ORCPT + 99 others); Fri, 23 Sep 2022 10:35:49 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:53130 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229612AbiIWOfr (ORCPT ); Fri, 23 Sep 2022 10:35:47 -0400 Received: from www262.sakura.ne.jp (www262.sakura.ne.jp [202.181.97.72]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 1ABA7F2749 for ; Fri, 23 Sep 2022 07:35:44 -0700 (PDT) Received: from fsav115.sakura.ne.jp (fsav115.sakura.ne.jp [27.133.134.242]) by www262.sakura.ne.jp (8.15.2/8.15.2) with ESMTP id 28NEZgEL063409; Fri, 23 Sep 2022 23:35:42 +0900 (JST) (envelope-from penguin-kernel@I-love.SAKURA.ne.jp) Received: from www262.sakura.ne.jp (202.181.97.72) by fsav115.sakura.ne.jp (F-Secure/fsigk_smtp/550/fsav115.sakura.ne.jp); Fri, 23 Sep 2022 23:35:42 +0900 (JST) X-Virus-Status: clean(F-Secure/fsigk_smtp/550/fsav115.sakura.ne.jp) Received: from [192.168.1.9] (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 28NEZgBr063406 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=NO); Fri, 23 Sep 2022 23:35:42 +0900 (JST) (envelope-from penguin-kernel@I-love.SAKURA.ne.jp) Message-ID: Date: Fri, 23 Sep 2022 23:35:43 +0900 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 6.3; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.3.0 Subject: Re: [PATCH] fs/ntfs3: fix negative shift size in true_sectors_per_clst() Content-Language: en-US To: Aleksandr Nogikh Cc: Randy Dunlap , Konstantin Komarov , Andrew Morton , Namjae Jeon , Shigeru Yoshida , Dmitry Vyukov , syzbot , "'Aleksandr Nogikh' via syzkaller-bugs" , ntfs3@lists.linux.dev, LKML References: <000000000000f8b5ef05dd25b963@google.com> <4b37f037-3b10-b4e4-0644-73441c8fa0af@I-love.SAKURA.ne.jp> <423b1fa6-10fa-3ff9-52bc-1262643c62d9@I-love.SAKURA.ne.jp> From: Tetsuo Handa In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,NICE_REPLY_A, SPF_HELO_NONE,SPF_NONE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2022/09/23 20:58, Aleksandr Nogikh wrote: > We do have plans to start inspecting LKML messages for the patches > that mention syzbot-reported bugs. It will be possible then to display > them all on the bug page and somehow mark bugs with a PATCH sent on > the list. I interpret it as an attempt to automatically show "Patch proposed" state. But since not all patches have Reported-by: tag, and/or a proposed patch with Reported-by: tag might be withdrawn via review, that state should be also manually changeable. > And then syzbot should just display all such received comments on the > bug's web page, right? Whether "all comments" or "last comment" needs some decision. It might be a few words indicating culprit subsystem (probably "last" should overwrite), it might be memo describing how far debugging went (probably "all" is helpful), it might be some URL where discussions/patches are (probably "all" is helpful), it might be trying to show or hide "Patch proposed" state (probably "last" should overwrite). By the way, a possible improvement on "Patch testing requests:" table. Although the "Patch" link showing diff output after applying proposed patch is OK, I'd like to also see a link to original "#syz test:" mail, for the intent of diff (which would be in patch description part if it was a formal patch) is dropped from diff output in the "Patch" link. For example, https://syzkaller.appspot.com/bug?extid=9ca7a12fd736d93e0232 was forgotten for 1000 days after 7 patch testing requests. I can't easily find the intent of each diff (e.g. just debug printk() or proper fix). It seems the last one was about to formal submit, but I can't find why it is not yet applied.