git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git (commit|tag) atomicity

From
ZBZach Brown <zab@zabbo.net>
Date
Feb 28, 2012, 18:57 UTC
Message-ID
<4F4D2391.9020701@zabbo.net>
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)
Previous: Jakub NarebskiNext: Jon Jagger
Message 5 of 6 in “git (commit|tag) atomicity”
  1. Jon JaggerFeb 28, 2012
  2. Holger HellmuthFeb 28, 2012
  3. Jon JaggerFeb 28, 2012
  4. Jakub NarebskiFeb 28, 2012
  5. Zach BrownFeb 28, 2012
  6. Jon JaggerFeb 28, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.