Received: by 2002:a05:6a10:6744:0:0:0:0 with SMTP id w4csp4048291pxu; Mon, 12 Oct 2020 08:12:32 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzq1JlTOUc85AMnWpeL4Bg+ErWtv79HKEdDCzxqw155yIQaKvqAlUbx608tWUz5SELYP3JO X-Received: by 2002:aa7:d30d:: with SMTP id p13mr14720903edq.315.1602515551853; Mon, 12 Oct 2020 08:12:31 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1602515551; cv=none; d=google.com; s=arc-20160816; b=Ll5HyjW1rXijENFnR7EPNeyawlsnx2bTd5b2HVCflmqw5CrwP5fC288dOXFgeaAMFI RhzogmYi+/YSqu/rXWOCdSIqP8+OYu9cFrMDrRRMXZPesnHknIZ9/o2TJvNEN2AQko3T EzFktOe3Et5E9c0vMeOrZslNX00Ekwv/rEIzmeZahOPZUoSkfTSVqhgUfKxWhB4IC9dz 0A2NyzZjNmWgE67eXB616Bop7NGF2ijdgb5F94zg0VqDM5ckqwrhRRuz+WRsyKYeUJcB 22dlwUIGlJgfmy6kASLFRLZQ+6DOaFq8F6V5SKUuFiK5YaNpl9K0XzLg3/E2BrkIf2WP NotQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:user-agent:references:message-id :in-reply-to:subject:cc:to:date:from:dkim-signature; bh=mkuNs+7XxlEVvtkC9IIAwWFcSgj3h27AZFQnWZFm0XA=; b=Ic/4FTuwOv8A24bdIDrtOJKBT5gE5Ta1X0LY63ejBCy9VSIu0PGzFpuAOa0IYoqNT9 lt5OLiMeitAkSLl4h3/HIz3pRB379OkAB8hFjXI71rjOQajxMYFbEHbUs2KHACx/fgTB acQUeMf6oWsvjKfNAxtLQOpO5vknLxrMG4brB9kycUNbRgsGmsBAMjXkLu4sSXg2OxmG 2xkctMrqFrNxDNp1bvVKCF0K8mWlVR5Xjl+QYbfmqExYwsuyFowqKC42MRIsQjTiCaLQ mOvd5sOhC6i8/sBuYNvpg9rN6k3YVkssLg9nJuB0Xd+Q8uJe+KVQzKgnIi8KmACIA1TK Za6w== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=lUD7+AsC; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id q16si3107637ejr.545.2020.10.12.08.12.08; Mon, 12 Oct 2020 08:12:31 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=lUD7+AsC; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2389431AbgJLPKZ (ORCPT + 99 others); Mon, 12 Oct 2020 11:10:25 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45084 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2388977AbgJLPKY (ORCPT ); Mon, 12 Oct 2020 11:10:24 -0400 Received: from mail-wr1-x442.google.com (mail-wr1-x442.google.com [IPv6:2a00:1450:4864:20::442]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 893A6C0613D0; Mon, 12 Oct 2020 08:10:24 -0700 (PDT) Received: by mail-wr1-x442.google.com with SMTP id t9so19583307wrq.11; Mon, 12 Oct 2020 08:10:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:date:to:cc:subject:in-reply-to:message-id:references :user-agent:mime-version; bh=mkuNs+7XxlEVvtkC9IIAwWFcSgj3h27AZFQnWZFm0XA=; b=lUD7+AsC3gIYyuLjGVkGz6YiVnzefUHoKy63QYSNowSifa9yEth6OS7GbALyfbMTnr LvGTXyj7YkXluF2uD9dqQnuvjVR8sebs6lreneRQ5UYklalKSg8hSwL7XtVYdSCITphA 6VmeQ8r4y2fXb8UQaxh/FVLnvuhzoyWwEaHfgjCtgA6EeO7agVwqK2i9dtf7U4DPMEMJ LSkgWoHtBoO8sD9NxY3EpZKVM+gxKt5WvICVfVYmWCRk6YWntGNc7G57vVSObnOVCAIo IMtIdelwKZzw7FmbW3qiIxI/3aCDdjnWAjhC82l+zk0ZJvGPVPq6q7bjlp3AmYTk8rZM 6KPw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:date:to:cc:subject:in-reply-to:message-id :references:user-agent:mime-version; bh=mkuNs+7XxlEVvtkC9IIAwWFcSgj3h27AZFQnWZFm0XA=; b=o2vGmNCz1MUut4ppU+ejY3KLXSpoC4kZ0q8aT1BoW6FXki+baAlgUlI8UG7Y8eNind GFrF72FHv6DDu5FPtZJynDwSGc0I7MnzdBZaLJQUEtEir9AbKVknU3rWCk9W9hLvIV5K e78jOAOPXFgKmrsv5BcS1FjPsW6aig/D/5RI1yODTDVFgdXik+f2NYShMTK2HF884Yas fVohy0mqN/DJnrlQYCKzSnQkvCsD7aeXcciT9uJ+8MKftmKhGPdeqY/JhWzPJ00hKxVn I5FQl4sMNBPXyqtXJ/L2zl/PwljnAubc7lBl0uo0vGU+TB0TiFF26TzEK/bK9gUUSqcx eryA== X-Gm-Message-State: AOAM531/QHT9uRorEPavkm3BXW/on2s3CwkZHTm84MlYWKbPPt71PSkt iEq9pROIoIyaJD4NOZ27svpMKjNCUfhgG1R3 X-Received: by 2002:adf:f305:: with SMTP id i5mr25025707wro.346.1602515423074; Mon, 12 Oct 2020 08:10:23 -0700 (PDT) Received: from felia ([2001:16b8:2d57:fc00:8472:203c:3ecb:c442]) by smtp.gmail.com with ESMTPSA id c185sm2406624wma.44.2020.10.12.08.10.21 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 12 Oct 2020 08:10:22 -0700 (PDT) From: Lukas Bulwahn X-Google-Original-From: Lukas Bulwahn Date: Mon, 12 Oct 2020 17:10:21 +0200 (CEST) X-X-Sender: lukas@felia To: Alan Stern cc: Lukas Bulwahn , Sudip Mukherjee , Greg Kroah-Hartman , linux-kernel@vger.kernel.org, linux-safety@lists.elisa.tech, linux-usb@vger.kernel.org Subject: Re: [linux-safety] [PATCH] usb: host: ehci-sched: add comment about find_tt() not returning error In-Reply-To: <20201012145710.GA631710@rowland.harvard.edu> Message-ID: References: <20201011205008.24369-1-sudipm.mukherjee@gmail.com> <20201012145710.GA631710@rowland.harvard.edu> User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 12 Oct 2020, Alan Stern wrote: > On Mon, Oct 12, 2020 at 04:11:38PM +0200, Lukas Bulwahn wrote: > > > > > > On Sun, 11 Oct 2020, Sudip Mukherjee wrote: > > > > > Add a comment explaining why find_tt() will not return error even though > > > find_tt() is checking for NULL and other errors. > > > > > > Signed-off-by: Sudip Mukherjee > > > > I get the intent of the comment but there is a large risk that somebody > > could remove the find_tt() call before the calling the function and there > > is no chance to then see later that the comment is actually wrong. > > Why would anybody do that? Who would deliberately go change a driver in > a way that is obviously wrong and would break it? Especially when such > changes are likely to cause compile errors? > > There are tons of changes one might make to any program that will leave > it syntactically valid but will cause it to fail. What's special about > removing the early calls to find_tt()? > > > I guess you want to link this comment here to a code line above and > > request anyone touching the line above to reconsider the comment then. > > That really seems unnecessary. > > > But there is no 'concept' for such kind of requests to changes and > > comments. > > > > So, the comment is true now, but might be true or wrong later. > > > > I am wondering if such comment deserves to be included if we cannot check > > its validity later... > > > > I would prefer a simple tool that could check that your basic assumption > > on the code is valid and if it the basic assumption is still valid, > > just shut up any stupid tool that simply does not get that these calls > > here cannot return any error. > > Real code contains so many assumptions, especially if you include ones > which are obvious to everybody, that such a tool seems impractical. > I fear that problem applies to all static code analysis tools I have seen; at some point, the remaining findings are simply obviously wrong to everybody but the tool does not get those assumptions and continues complaining, making the tool seem impractical. Alan, so would you be willing to take patches where _anyone_ simply adds comments on what functions returns, depending on what this person might consider just not obvious enough? Or are you going to simply reject this 'added a comment' patch here? I am not arguing either way, it is just that it is unclear to me what the added value of the comment really is here. And for the static analysis finding, we need to find a way to ignore this finding without simply ignoring all findings or new findings that just look very similar to the original finding, but which are valid. Lukas