public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: Zach Brown <zab@zabbo•net>
To: Jakub Narebski <jnareb@gmail•com>
Cc: Jon Jagger <jon@jaggersoft•com>,
	git@vger•kernel.org, Holger Hellmuth <hellmuth@ira•uka.de>
Subject: Re: git (commit|tag) atomicity
Date: Tue, 28 Feb 2012 13:57:21 -0500	[thread overview]
Message-ID: <4F4D2391.9020701@zabbo.net> (raw)
In-Reply-To: <m3aa42vosb.fsf@localhost.localdomain>


It's a bit of a tangent, but just to be sure people don't get the wrong
impression..

> But I am not sure... that probably depends on how opendir(3) and
> readdir(3) works on given filesystem wrt. updates to opened directory.
> I think VFS on Linux ensures that you see view of filesystem as it was
> on opendir().

No, readdir() does not give you a static view of the entries in a
directory as it was on opendir().  readdir() will reflect modifications
that are done after opendir().  The specifics for a given situation
depend on how the file system maps the readdir position (f_pos) to
directory entries.  You can see very different results when comparing,
say, stock ext2, indexed ext[34], and btrfs.

- z
(your message probably caught my eye because telldir()/seekdir() is
*loathed* by file system designers)

  reply	other threads:[~2012-02-28 19:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-28 15:40 git (commit|tag) atomicity Jon Jagger
2012-02-28 16:46 ` Holger Hellmuth
2012-02-28 17:12   ` Jon Jagger
2012-02-28 17:41     ` Jakub Narebski
2012-02-28 18:57       ` Zach Brown [this message]
2012-02-28 20:43         ` Jon Jagger

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=4F4D2391.9020701@zabbo.net \
    --to=zab@zabbo$(echo .)net \
    --cc=git@vger$(echo .)kernel.org \
    --cc=hellmuth@ira$(echo .)uka.de \
    --cc=jnareb@gmail$(echo .)com \
    --cc=jon@jaggersoft$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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