From: Johannes Sixt <j.sixt@viscovery.net>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org, git-dev@github.com,
"Shawn O. Pearce" <spearce@spearce.org>,
Nicolas Pitre <nico@fluxnic.net>
Subject: Re: [PATCH] pack-objects: protect against disappearing packs
Date: Fri, 14 Oct 2011 09:06:11 +0200 [thread overview]
Message-ID: <4E97DF63.104@viscovery.net> (raw)
In-Reply-To: <20111014012320.GA4395@sigill.intra.peff.net>
Am 10/14/2011 3:23, schrieb Jeff King:
> In practice, however, adding this check still has value, for
> three reasons.
>
> 1. If you have a reasonable number of packs and/or a
> reasonable file descriptor limit, you can keep all of
> your packs open simultaneously. If this is the case,
> then the race is impossible to trigger.
On Windows, we cannot remove files that are open. If I understand
correctly, this patch keeps more files open for a longer time. Is there
any chance that packfiles remain now open until an unlink() call?
I am not worried about parallel processes (we already have a problem
there), but that this can now happen within a single process, i.e., that a
single git-repack -a -d -f would now try to unlink a pack file that it
opened itself and did not close timely.
I'll test your patch later this weekend to see whether the test suite
finds something. But perhaps you know the answer already?
-- Hannes
next prev parent reply other threads:[~2011-10-14 7:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-14 1:23 [PATCH] pack-objects: protect against disappearing packs Jeff King
2011-10-14 1:31 ` Jeff King
2011-10-14 2:43 ` Nicolas Pitre
2011-10-14 2:42 ` Nicolas Pitre
2011-10-14 13:02 ` Jeff King
2011-10-14 7:06 ` Johannes Sixt [this message]
2011-10-14 13:07 ` Jeff King
2011-10-14 14:35 ` Johannes Sixt
2011-10-14 18:03 ` [PATCH 1/2] " Jeff King
2011-10-14 18:04 ` [PATCH 2/2] downgrade "packfile cannot be accessed" errors to warnings Jeff King
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=4E97DF63.104@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=git-dev@github.com \
--cc=git@vger.kernel.org \
--cc=nico@fluxnic.net \
--cc=peff@peff.net \
--cc=spearce@spearce.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).