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: <1253968675.4568.3.camel@ht.satnam>
Date:	Sat, 26 Sep 2009 18:07:55 +0530
From:	Jaswinder Singh Rajput <jaswinder@...nel.org>
To:	"Robert P. J. Day" <rpjday@...shcourse.ca>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: how best to report results of my kernel tree scanning scripts?

Hello Robert,

On Sat, 2009-09-26 at 08:16 -0400, Robert P. J. Day wrote:
> 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
> 

Thanks for reporting these results, I will try to fix them and submit
patches with Reported-by: Robert P. J. Day <rpjday@...shcourse.ca>

Thanks,
--
JSR

--
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