[kernel-sec-discuss] r2018 - active

[Michael Gilbert]

On Tue,  9 Nov 2010 15:56:55 +0000, Moritz Muehlenhoff wrote:
> Author: jmm
> Date: 2010-11-09 15:56:38 +0000 (Tue, 09 Nov 2010)
> New Revision: 2018
> 
> Modified:
>    active/CVE-2010-3442
>    active/CVE-2010-3858
>    active/CVE-2010-3873
>    active/CVE-2010-4075
> Log:
> upstream fixes
> 
> 
> Modified: active/CVE-2010-3442
> ===================================================================
> --- active/CVE-2010-3442	2010-11-08 15:13:02 UTC (rev 2017)
> +++ active/CVE-2010-3442	2010-11-09 15:56:38 UTC (rev 2018)
> @@ -15,6 +15,7 @@
>  References:
>   http://git.kernel.org/?p=linux/kernel/git/tiwai/sound-2.6.git;a=commitdiff;h=5591bf07225523600450edd9e6ad258bb877b779
>  Notes:
> + jmm> 5591bf07225523600450edd9e6ad258bb877b779
>  Bugs:
>  upstream: released (2.6.36)
>  2.6.32-upstream-stable: released (2.6.32.25)

According to active/00examples, the patch/commit is supposed to be
included in brackets following the fixed version.  Not that formatting
is that big of a deal or anything, but it does make things a bit more
consistent/cleaner.  Also, the stable tree has a different commit, so
this tracking eliminates that ambiguity. e.g. for this case:

  upstream: released (2.6.36) [5591bf07]
  2.6.32-upstream-stable: released (2.6.32.25) [08f00ae2]

You can use scripts/find-commit to figure out the stable commit number.

Mike