linux-kernel - Re: arm64: USB_ARCH_HAS

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <alpine.DEB.2.02.1501282106540.19947@utopia.booyaka.com>
Date:	Wed, 28 Jan 2015 21:12:42 +0000 (UTC)
From:	Paul Walmsley <paul@...an.com>
To:	Paul Bolle <pebolle@...cali.nl>
cc:	Valentin Rothberg <valentinrothberg@...il.com>,
	Thierry Reding <treding@...dia.com>,
	Catalin Marinas <catalin.marinas@....com>,
	Will Deacon <will.deacon@....com>,
	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: arm64: USB_ARCH_HAS_EHCI

Hi Paul,

On Wed, 28 Jan 2015, Paul Bolle wrote:

> On Wed, 2015-01-28 at 16:25 +0000, Paul Walmsley wrote:
> > Is the Kconfig checker script you mentioned on Tuesday available in the 
> > mainline tree?  I don't see anything obvious under the "Static Analysers" 
> > section of the Makefile, but perhaps I'm overlooking it.
> 
> No, it's not.
> 
> In tree you'll find scripts/checkkconfigsymbols.py. That catches over
> 90% of the stuff my local script catches, in less than 10% of runtime.
> It would certainly have caught your use of USB_ARCH_HAS_EHCI.

OK great, I'll add that to my static analysis scripts.

> My local script is my third (or fourth) attempt at a script that checks
> these kind of issues. I've used it on linux-next since for about 3/4 of
> a year now. While doing that I ran into people that are planning into
> adding similar, but far more advanced, functionality into one of the
> bots that is checking linux. So I never bothered making my script
> public. (I'm not sure what the status of those plan is now.)
> 
> In the mean time I'll keep on checking linux-next with my script. That
> should also help to see what problems an actual bot could run into, for
> the benefit of those people. 

That sounds good; it's a very useful service you're providing.

> Problems like:
> - should it check each commit (I think it should only check releases);
> - should it be a true bot (I think it needs a wetware frontend to
>   filter out non-issues).
> 
> Hope this answers your question.

It does.  Thanks for the detailed response.


- Paul
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/