Jeff King fd9a631c56 revision: avoid out-of-bounds read/write on empty pathspec
Running t4216 with ASan results in it complaining of an out-of-bounds
read in prepare_to_use_bloom_filter(). The issue is this code to strip a
trailing slash:

  last_index = pi->len - 1;
  if (pi->match[last_index] == '/') {

because we have no guarantee that pi->len isn't zero. This can happen if
the pathspec is ".", as we translate that to an empty string. And if
that read of random memory does trigger the conditional, we'd then do an
out-of-bounds write:

  path_alloc = xstrdup(pi->match);
  path_alloc[last_index] = '\0';

Let's make sure to check the length before subtracting. Note that for an
empty pathspec, we'd end up bailing from the function a few lines later,
which makes it tempting to just:

  if (!pi->len)
          return;

early here. But our code here is stripping a trailing slash, and we need
to check for emptiness after stripping that slash, too. So we'd have two
blocks, which would require repeating some cleanup code.

Instead, just skip the trailing-slash for an empty string. Setting
last_index at all in the case is awkward since it will have a nonsense
value (and it uses an "int", which is a too-small type for a string
anyway). So while we're here, let's:

  - drop last_index entirely; it's only used in two spots right next to
    each other and writing out "pi->len - 1" in both is actually easier
    to follow

  - use xmemdupz() to duplicate the string. This is slightly more
    efficient, but more importantly makes the intent more clear by
    allocating the correct-sized substring in the first place. It also
    eliminates any question of whether path_alloc is as long as
    pi->match (which it would not be if pi->match has any embedded NULs,
    though in practice this is probably impossible).

Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2020-08-04 09:31:02 -07:00
2020-06-17 21:54:03 -07:00
2020-08-01 13:49:14 -07:00
2020-06-22 11:21:07 -07:00
2020-05-01 13:39:59 -07:00
2020-03-05 10:43:02 -08:00
2020-03-25 13:57:41 -07:00
2020-03-25 13:57:41 -07:00
2020-04-28 10:47:10 -07:00
2019-09-28 14:04:16 +09:00
2019-11-20 13:29:02 +09:00
2019-11-18 15:21:28 +09:00
2019-11-18 15:21:28 +09:00
2020-03-30 10:59:08 -07:00
2020-02-19 09:37:15 -08:00
2020-04-16 15:38:06 -07:00
2020-06-08 18:06:26 -07:00
2019-07-09 15:25:44 -07:00
2020-03-24 15:04:44 -07:00
2019-12-01 09:04:36 -08:00
2020-07-06 22:09:13 -07:00
2020-07-06 22:09:13 -07:00
2019-11-10 16:00:54 +09:00
2019-05-05 15:20:10 +09:00
2019-12-25 11:21:58 -08:00
2020-03-10 11:41:40 -07:00
2020-07-06 22:09:13 -07:00
2020-03-24 15:04:43 -07:00
2019-07-25 13:59:20 -07:00
2020-07-26 18:01:43 -07:00
2019-11-18 15:21:28 +09:00
2019-11-10 16:00:54 +09:00
2020-07-28 14:28:15 -07:00
2020-05-12 22:02:17 -07:00
2020-06-25 12:27:47 -07:00
2020-06-25 12:27:47 -07:00
2019-04-22 11:14:43 +09:00
2020-06-08 18:06:26 -07:00
2019-11-18 15:21:28 +09:00
2020-05-01 13:39:55 -07:00
2019-12-01 09:04:35 -08:00
2020-04-15 09:20:29 -07:00
2019-05-05 15:20:10 +09:00
2020-04-29 16:15:27 -07:00
2020-04-10 09:28:02 -07:00
2019-12-16 13:08:39 -08:00
2020-07-06 22:09:13 -07:00
2020-07-06 22:09:13 -07:00
2018-11-02 12:14:21 +09:00
2020-03-24 15:04:44 -07:00
2020-03-24 15:04:44 -07:00
2020-07-16 10:42:52 -07:00
2018-08-15 15:08:23 -07:00
2020-08-01 13:49:13 -07:00
2020-07-06 22:09:17 -07:00
2019-04-01 11:57:39 +09:00
2020-07-30 13:20:36 -07:00
2019-11-10 16:00:54 +09:00
2020-04-29 16:15:27 -07:00
2020-04-29 16:15:27 -07:00
2020-07-06 22:09:13 -07:00
2019-05-05 15:20:10 +09:00
2020-04-28 15:49:56 -07:00
2019-11-13 10:09:10 +09:00
2019-02-05 14:26:11 -08:00
2019-11-18 15:21:29 +09:00
2018-12-09 12:37:32 +09:00
2019-09-05 14:10:18 -07:00
2020-07-06 22:09:13 -07:00
2020-07-06 22:09:13 -07:00
2019-11-10 16:00:54 +09:00
2020-05-08 14:25:01 -07:00
2018-10-19 13:34:02 +09: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). To subscribe to the list, send an email with just "subscribe git" in the body to majordomo@vger.kernel.org. The mailing list archives are available at https://lore.kernel.org/git/, http://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 582 MiB
Languages
C 50.5%
Shell 38.7%
Perl 4.5%
Tcl 3.2%
Python 0.8%
Other 2.1%