linux-kernel - how to properly post/disseminate kernel cleanup/janitorial possibilities?

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:	Mon, 27 Apr 2009 16:46:46 -0400 (EDT)
From:	"Robert P. J. Day" <rpjday@...shcourse.ca>
To:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: how to properly post/disseminate kernel cleanup/janitorial
 possibilities?

  since i, on an occasional basis, run a set of scanning scripts i
wrote and promptly annoy the crap out of everyone with the results,
i'm open to the proper way to do this scanning and get the results out
there to people who might be interested while not bugging those folks
who aren't.

  a while back, a few people suggested a wiki page, while others
disagreed, suggesting that no one will follow a link to a wiki page
and will only read what's directly on the list.  grapple, grapple.

  in the end (as i'm sure you're aware by now), i post the results
here:

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

i'm convinced that there's value in the links i've promoted lately --
scanning Kconfig files for unused or "bad" CONFIG variables, not just
to clean historical cruft out of those files but because, on occasion,
the scanning really does track down typoes and errors.

  not quite so critical is a "style" script i wrote, which looks for
places to simplify code by using some of the macros/functions defined
in include/linux/kernel.h.  i ran that script again earlier today, and
posted only *some* of the results here:

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

long story short, i have a *pile* of scripts and sub-scripts i'm happy
to run and post the results of since it takes practically zero time on
my part, i'm just open to what folks think is the most productive way
to do that, and also for any other scanning i can add since, by now,
any other patterns to scan for would just represent adding a line or
two to a script.

 thoughts?

rday
--

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

        Linux Consulting, Training and Annoying Kernel Pedantry.

Web page:                                          http://crashcourse.ca
Linked In:                             http://www.linkedin.com/in/rpjday
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/