linux-kernel - Re: any value in running my kernel scanning scripts before release?

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <4C3F0D1B.9060403@suse.cz>
Date:	Thu, 15 Jul 2010 15:28:59 +0200
From:	Michal Marek <mmarek@...e.cz>
To:	"Robert P. J. Day" <rpjday@...shcourse.ca>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linux-input@...r.kernel.org
Subject: Re: any value in running my kernel scanning scripts before release?

On 07/15/2010 01:32 PM, Robert P. J. Day wrote:
> 
>   normally i wait for the merge window, then run my kernel scanning
> scripts and post results.  any interest in me doing that earlier?  i
> just did a quick test and found a number of incongruities like, for
> example:
> 
> $ grep -r "config QT2160" *
> drivers/input/keyboard/Kconfig:config QT2160
> $
> 
> $ grep -r KEYBOARD_QT2160 *
> drivers/input/keyboard/Makefile:obj-$(CONFIG_KEYBOARD_QT2160) += qt2160.o
> $

These are plain bugs, so it's IMO OK to send fixes for these at any time
before the final release. In the worst case, it will be merged after the
final release.

just my two cents,
Michal
--
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/