linux-kernel - Re: Linux 3.0.8

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: <20111027120840.GA6863@suse.de>
Date:	Thu, 27 Oct 2011 14:08:40 +0200
From:	Greg KH <gregkh@...e.de>
To:	Paul Bolle <pebolle@...cali.nl>
Cc:	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	torvalds@...ux-foundation.org, stable@...r.kernel.org, lwn@....net
Subject: Re: Linux 3.0.8

On Thu, Oct 27, 2011 at 02:02:49PM +0200, Paul Bolle wrote:
> On Tue, 2011-10-25 at 07:19 +0200, Greg KH wrote:
> > The updated 3.0.y git tree can be found at (NOTE THE ADDRESS CHANGE):
> >         git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-3.0.y
> > and can be browsed at the normal kernel.org git web browser:
> >         http://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=summary
> 
> Somehow I seem to be able to generate perfect copies of patch-3.0.4.bz2
> (and earlier), by simply doing a command like:
>     git diff v3.0 v3.04 | bzip2 -9 > patch-3.0.4-git.bz2 
> 
> But for patch-3.0.5 (and above) trivial commands like
>      git diff v3.0 v3.0.8 > patch-3.0.8-git
> 
> do not generate perfect copies anymore. Have you perhaps changed the way
> you generate the patches since v3.0.5?  Not that this matters much,
> since tags v3.0.5 (and up) are signed by your "Linux kernel stable
> release signing key", but I still wonder what could cause this
> difference. Maybe it's just a git upgrade on your side.

We have found out that different versions of git will generate different
patches.  The end result of the patch when you apply it will always be
the same, but this is a non-trivial problem to solve.

That's why we generate the patches on our local machine and upload them,
instead of just generating the signature and having the server create
it.

Can you verify that the end result from your patch, and my patch,
produces the same tree?  If not, we need to resolve that.

thanks,

greg k-h
--
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/