Jeff King 67a6b1aeb8 unpack_loose_header(): avoid numeric comparison of zlib status
When unpacking a loose header, we try to inflate the first 32 bytes.
We'd expect either Z_OK (we filled up the output buffer, but there are
more bytes in the object) or Z_STREAM_END (this is a tiny object whose
header and content fit in the buffer).

We check for that with "if (status < Z_OK)", making the assumption that
all of the errors we'd see have negative values (as Z_OK itself is "0",
and Z_STREAM_END is "1").

But there's at least one case this misses: Z_NEED_DICT is "2". This
isn't something we'd ever expect to see, but if we do see it, we should
consider it an error (since we have no dictionary to load).

Instead, the current code interprets Z_NEED_DICT as success and looks
for the object header's terminating NUL in the bytes we've read. This
will generaly be zero bytes if the dictionary is mentioned at the start
of the stream. So we'll fail to find it and complain "the header is too
long" (ULHR_LONG). But really, the problem is that the object is
malformed, and we should return ULHR_BAD.

This is a minor bug, as we consider both cases to be an error. But it
does mean we print the wrong error message. The test case added in the
previous patch triggers this code, so we can just confirm the error
message we see here.

Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2025-02-25 10:24:55 -08:00
2024-11-26 22:14:59 +01:00
2024-11-26 22:14:59 +01:00
2024-02-14 15:36:06 -08:00
2024-11-26 22:15:00 +01:00
2023-12-14 14:38:07 -08:00
2024-02-18 21:03:43 +08:00
2024-01-18 11:53:17 -08:00
2023-12-26 12:04:32 -08:00
2023-12-26 12:04:32 -08:00
2024-01-23 10:40:10 -08:00
2024-11-26 22:14:59 +01:00
2024-11-26 22:14:58 +01:00
2024-01-08 14:05:15 -08:00
2024-02-15 15:14:48 -08:00
2024-04-19 12:38:54 +02:00
2024-04-19 12:38:50 +02:00
2024-04-19 12:38:50 +02:00
2024-11-26 22:15:00 +01:00
2024-04-19 12:38:50 +02:00
2023-12-26 12:04:32 -08:00
2024-04-19 12:38:50 +02:00
2023-12-14 14:38:08 -08:00
2024-04-19 12:38:54 +02:00
2024-04-19 12:38:46 +02:00
2024-04-19 12:38:54 +02:00
2024-01-08 14:05:15 -08:00
2024-11-26 22:15:00 +01:00
2024-04-19 12:38:54 +02:00
2024-01-08 14:05:15 -08:00
2024-04-19 12:38:54 +02:00
2024-04-19 12:38:54 +02:00
2024-04-19 12:38:54 +02:00
2023-12-27 14:52:24 -08:00
2024-11-26 22:14:59 +01:00
2024-11-26 22:14:59 +01:00
2024-04-19 12:38:50 +02:00
2024-04-19 12:38:37 +02:00

Build status

Git - fast, scalable, distributed revision control system

Git is a fast, scalable, distributed revision control system with an unusually rich command set that provides both high-level operations and full access to internals.

Git is an Open Source project covered by the GNU General Public License version 2 (some parts of it are under different licenses, compatible with the GPLv2). It was originally written by Linus Torvalds with help of a group of hackers around the net.

Please read the file INSTALL for installation instructions.

Many Git online resources are accessible from https://git-scm.com/ including full documentation and Git related tools.

See Documentation/gittutorial.txt to get started, then see Documentation/giteveryday.txt for a useful minimum set of commands, and Documentation/git-<commandname>.txt for documentation of each command. If git has been correctly installed, then the tutorial can also be read with man gittutorial or git help tutorial, and the documentation of each command with man git-<commandname> or git help <commandname>.

CVS users may also want to read Documentation/gitcvs-migration.txt (man gitcvs-migration or git help cvs-migration if git is installed).

The user discussion and development of Git take place on the Git mailing list -- everyone is welcome to post bug reports, feature requests, comments and patches to git@vger.kernel.org (read Documentation/SubmittingPatches for instructions on patch submission and Documentation/CodingGuidelines).

Those wishing to help with error message, usage and informational message string translations (localization l10) should see po/README.md (a po file is a Portable Object file that holds the translations).

To subscribe to the list, send an email to git+subscribe@vger.kernel.org (see https://subspace.kernel.org/subscribing.html for details). The mailing list archives are available at https://lore.kernel.org/git/, https://marc.info/?l=git and other archival sites.

Issues which are security relevant should be disclosed privately to the Git Security mailing list git-security@googlegroups.com.

The maintainer frequently sends the "What's cooking" reports that list the current status of various development topics to the mailing list. The discussion following them give a good reference for project status, development direction and remaining tasks.

The name "git" was given by Linus Torvalds when he wrote the very first version. He described the tool as "the stupid content tracker" and the name as (depending on your mood):

  • random three-letter combination that is pronounceable, and not actually used by any common UNIX command. The fact that it is a mispronunciation of "get" may or may not be relevant.
  • stupid. contemptible and despicable. simple. Take your pick from the dictionary of slang.
  • "global information tracker": you're in a good mood, and it actually works for you. Angels sing, and a light suddenly fills the room.
  • "goddamn idiotic truckload of sh*t": when it breaks
Description
No description provided
Readme 637 MiB
Languages
C 50.5%
Shell 38.7%
Perl 4.5%
Tcl 3.2%
Python 0.8%
Other 2.1%