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-next>] [day] [month] [year] [list]
Date:	Sat, 26 Sep 2009 08:16:12 -0400 (EDT)
From:	"Robert P. J. Day" <rpjday@...shcourse.ca>
To:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: how best to report results of my kernel tree scanning scripts?


  since the merge window appears to be ready to close fairly soon(?),
i'm prepping to run my scanning scripts once again to identify (among
other things):

  * unused Kconfig CONFIG variables
  * references to CONFIG_ variables that don't even exist (both in
    source files and Makefiles)
  * references to non-existent header files

and bunches of other things.  i'm open as to the best way to post the
results, since different people have different opinions.

  and, no, i can't just submit patches since, in many cases, i have no
idea what the fix should be (if any) -- that's the kind of decision
best left to the respective subsystem maintainers.

  thoughts?  this is where i put the old output:

http://www.crashcourse.ca/wiki/index.php/Kernel_cleanup

rday
--

========================================================================
Robert P. J. Day                               Waterloo, Ontario, CANADA

        Linux Consulting, Training and Annoying Kernel Pedantry.

Web page:                                          http://crashcourse.ca
Twitter:                                       http://twitter.com/rpjday
========================================================================
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ