linux-kernel - Re: Linux v2.6.18-rc3

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]

Date:	Mon, 31 Jul 2006 01:02:25 -0700
From:	Junio C Hamano <junkio@....net>
To:	Russell King <rmk+lkml@....linux.org.uk>
cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...l.org>
Subject: Re: Linux v2.6.18-rc3

Russell King <rmk+lkml@....linux.org.uk> writes:

> There's something weird in this release - object
> 0021aad5db43ccc0d0356f2f5e4e28446c8b983a appears to change size (or it
> does for me.)

This is a manifestation of a recent harmless change which allows
you to change the compression level for loose objects, which
happened on July 3rd (v1.4.1-g12f6c30).  The blob is compressed
to 6891 bytes with zlib compression level of 6 (new default)
while older git used compression level of 9 (old default,
without a possibility for users to futz with it) which produces
6862 bytes.

Linus is apparently using newer git that uses the new default,
while -mmc, -rmk, and -serial trees are managed with git older
than the said version.

    commit 12f6c308d53509dcb11e309604457d21d60438db
    Author: Joachim B Haga <cjhaga@....uio.no>
    Date:   Mon Jul 3 22:11:47 2006 +0200

        Make zlib compression level configurable, and change default.

        With the change in default, "git add ." on kernel dir is about
        twice as fast as before, with only minimal (0.5%) change in
        object size. The speed difference is even more noticeable
        when committing large files, which is now up to 8 times faster.

        The configurability is through setting core.compression = [-1..9]
        which maps to the zlib constants; -1 is the default, 0 is no
        compression, and 1..9 are various speed/size tradeoffs, 9
        being slowest.

        Signed-off-by: Joachim B Haga (cjhaga@....uio.no)
        Acked-by: Linus Torvalds <torvalds@...l.org>
        Signed-off-by: Junio C Hamano <junkio@....net>

As you have found out, the objects compressed differently are
fully backward compatible and there is nothing to worry about.

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