From: "Lukas Bulwahn" <lukas.bulwahn@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Lukas Bulwahn <lukas.bulwahn@gmail.com>,
Alan Stern <stern@rowland.harvard.edu>,
Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
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
Date: Mon, 12 Oct 2020 20:25:30 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.2010122022250.17866@felia> (raw)
In-Reply-To: <20201012151816.GA1559916@kroah.com>
On Mon, 12 Oct 2020, Greg Kroah-Hartman wrote:
> On Mon, Oct 12, 2020 at 05:10:21PM +0200, Lukas Bulwahn wrote:
> > 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.
>
> Then I suggest you fix the tool that "flagged" this, surely this is not
> the only thing it detected with a test like this, right?
>
> What tool reported this?
>
Sudip and I are following on clang analyzer findings.
On linux-next, there is new build target 'make clang-analyzer' that
outputs a bunch of warnings, just as you would expect from such static
analysis tools.
We will fix the tool if we can.
Lukas
next prev parent reply other threads:[~2020-10-12 18:25 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-11 20:50 [PATCH] usb: host: ehci-sched: add comment about find_tt() not returning error Sudip Mukherjee
2020-10-12 0:27 ` Alan Stern
2020-10-12 14:11 ` [linux-safety] " Lukas Bulwahn
2020-10-12 14:57 ` Alan Stern
2020-10-12 15:10 ` Lukas Bulwahn
2020-10-12 15:18 ` Greg Kroah-Hartman
2020-10-12 18:25 ` Lukas Bulwahn [this message]
2020-10-13 5:23 ` Greg Kroah-Hartman
2020-10-13 5:37 ` Lukas Bulwahn
2020-10-13 6:36 ` Greg Kroah-Hartman
2020-10-13 7:16 ` Lukas Bulwahn
2020-10-13 7:35 ` Greg Kroah-Hartman
2020-10-13 8:02 ` Lukas Bulwahn
2020-10-13 8:24 ` Sudip Mukherjee
2020-10-13 8:36 ` Lukas Bulwahn
2020-10-12 16:00 ` Alan Stern
2020-10-12 18:17 ` Lukas Bulwahn
2020-10-13 5:21 ` Greg Kroah-Hartman
2020-10-13 5:41 ` Lukas Bulwahn
2020-10-12 15:24 ` Sudip Mukherjee
2020-10-12 18:49 ` Lukas Bulwahn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.21.2010122022250.17866@felia \
--to=lukas.bulwahn@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-safety@lists.elisa.tech \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=sudipm.mukherjee@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox