git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Alex Netkachov <alex.netkachov@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Potential bug in pack-objects.c
Date: Tue, 22 Jan 2019 02:29:46 -0500	[thread overview]
Message-ID: <20190122072946.GB28975@sigill.intra.peff.net> (raw)
In-Reply-To: <CAGAu0HVeQFA_O8_hsZbzRi9X35fF3DAeUaSd993JF=NTwaZP1Q@mail.gmail.com>

On Mon, Jan 21, 2019 at 10:10:16PM +0000, Alex Netkachov wrote:

> On the location builtin/pack-objects.c:1996 the code tries to set
> read_lock (pthread_mutex_lock(&read_mutex)) and fails. I suspect that
> read_mutex is not initialised yet. It is initialised in
> init_threaded_search, which is called later in prepare_pack (through
> ll_find_deltas).

This sounds like the same bug being discussed in:

  http://public-inbox.org/git/20190118022736.36832-1-phogg@novamoon.net/

-Peff

  reply	other threads:[~2019-01-22  7:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-21 22:10 Potential bug in pack-objects.c Alex Netkachov
2019-01-22  7:29 ` Jeff King [this message]
2019-01-22 15:33   ` Alex Netkachov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190122072946.GB28975@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=alex.netkachov@gmail.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).