From: "Shawn O. Pearce" <spearce@spearce.org>
To: Robin Rosenberg <robin.rosenberg@dewire.com>
Cc: git@vger.kernel.org
Subject: [JGIT PATCH (RESEND) 0/4] Fix race condition on loading pack files
Date: Wed, 12 Aug 2009 12:45:19 -0700 [thread overview]
Message-ID: <1250106323-19408-1-git-send-email-spearce@spearce.org> (raw)
I had sent this series while you were on vacation, so I assume it
just got lost in the shuffle and am resending.
This series tries to fix a "racy git" problem when reading pack
files in a repository; its possible that the directory is modified,
read and modified again in the same filesystem timestamp, resulting
in the reader not noticing the second modification. This may cause
a reader to lose access to objects on disk.
Shawn O. Pearce (4):
Avoid unnecessary stat when scanning packs in the objects directory
Make ObjectDirectory last modified time atomically updated with list
Don't create new pack lists if the directory hasn't changed
Fix racy condition when a repository is repacked
.../src/org/spearce/jgit/lib/ObjectDirectory.java | 235 ++++++++++++-------
1 files changed, 148 insertions(+), 87 deletions(-)
next reply other threads:[~2009-08-12 19:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-12 19:45 Shawn O. Pearce [this message]
2009-08-12 19:45 ` [JGIT PATCH (RESEND) 1/4] Avoid unnecessary stat when scanning packs in the objects directory Shawn O. Pearce
2009-08-12 19:45 ` [JGIT PATCH (RESEND) 2/4] Make ObjectDirectory last modified time atomically updated with list Shawn O. Pearce
2009-08-12 19:45 ` [JGIT PATCH (RESEND) 3/4] Don't create new pack lists if the directory hasn't changed Shawn O. Pearce
2009-08-12 19:45 ` [JGIT PATCH (RESEND) 4/4] Fix racy condition when a repository is repacked Shawn O. Pearce
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=1250106323-19408-1-git-send-email-spearce@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=robin.rosenberg@dewire.com \
/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