Johannes Schindelin c3a6be2333 midx: validate incremental MIDX pack IDs
Incremental MIDX support made object-offset pack IDs local to each layer
and then converted them to chain-global IDs by adding
`num_packs_in_base`. The conversion was introduced by 19419821ba
(midx: teach `nth_midxed_pack_int_id()` about incremental MIDXs,
2024-08-06). Chain-aware pack preparation followed in 1820bd878c
(midx: teach `prepare_midx_pack()` about incremental MIDXs, 2024-08-06),
but the final `midx_fill_entry()` lookup remained tied to the original
layer. Only with 8f909ff4e9 (packfile: recover when a multi-pack-index
names a removed pack, 2026-08-29) did Coverity point out this issue: a
local ID such as `UINT32_MAX` could wrap when the base-pack count was
added, producing a plausible but incorrect global ID. After
`prepare_midx_pack()` resolved the chain, `midx_fill_entry()` could then
underflow or address the wrong layer while indexing the current layer's
pack array, causing an invalid memory access and crashing Git.

Validate each local pack ID against its layer's pack count before adding
the base count, and obtain the final pack through `nth_midxed_pack()`,
which resolves the correct MIDX layer. This prevents an invalid local ID
from wrapping during conversion and ensures that the lookup uses the
layer identified by the resolved chain-global ID.

Assisted-by: GPT-5.6 Luna
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2026-09-17 12:43:46 -07:00
2026-09-16 09:04:55 -07:00
2026-09-16 09:07:56 -07:00
…
2026-09-15 11:07:37 -07:00
…
2026-09-15 11:07:37 -07:00
2026-05-21 12:06:48 +09:00
…
…
…
…
…
…
…
…
…
…
…
…
…
…
…
…
2026-05-21 12:06:48 +09:00
2026-02-23 13:23:41 -08:00
2026-02-23 13:23:41 -08:00
…
…
2026-06-08 00:21:35 +09:00
…
2026-07-16 14:10:08 -07:00
2026-07-16 14:10:08 -07:00
…
…
2026-06-05 22:27:24 +09:00
…
2026-05-30 07:07:27 +09:00
2026-08-24 13:17:51 -07:00
2026-05-30 07:07:27 +09:00
2026-07-30 10:32:03 -07:00
…
…
2026-03-23 08:33:10 -07:00
…
…
…
2026-09-16 09:07:56 -07:00
…
…
…
…
…
…
…
2026-05-14 15:59:25 +09:00
2026-05-14 15:59:25 +09:00
2026-06-15 07:42:00 -07:00
2026-07-16 23:05:47 -07:00
…
…
2026-09-14 14:02:52 -07:00
…
…
…
…
…
2026-07-15 13:24:19 -07:00
…
…
2026-09-16 09:04:55 -07:00
2026-07-31 08:52:16 -07:00
2026-07-31 08:52:16 -07:00
…
…
…
2026-09-15 11:07:37 -07:00
2026-09-15 11:07:37 -07:00
…
…
2026-05-15 04:50:45 +09:00
2026-05-15 04:50:45 +09:00
…
2026-07-06 15:50:23 -07:00
2026-06-09 10:04:50 +09:00
…
…
2026-05-19 12:14:03 +09:00
2026-05-19 12:14:03 +09:00
2026-08-23 11:11:07 +02:00
…
…
…
2026-07-06 15:50:25 -07:00
…
2026-07-07 10:49:40 -07:00
…
2026-08-18 09:31:36 -07:00
2026-05-13 00:48:42 +09:00
…
…
…
…
…
…
2026-07-14 12:54:25 -07:00
2026-07-14 12:54:25 -07:00
…
…
2026-07-07 10:49:40 -07:00
…
2026-05-30 07:07:27 +09:00
…
2026-09-07 09:32:05 -07:00
2026-07-23 07:14:34 -07:00
…
…
…
…
…
…
…
…
…

GitHub build status GitLab 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.adoc to get started, then see Documentation/giteveryday.adoc for a useful minimum set of commands, and Documentation/git-<commandname>.adoc 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.adoc (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
Languages
C 49.8%
Shell 39.8%
Perl 4.3%
Tcl 3%
Python 0.8%
Other 2.1%