Bug#898287: Subject: disorderfs inode on getdents

[Omar Navarro Leija]

Hello,

I'm currently leading a research project on deterministic execution of
programs. We're developing a tool to enforce determinism dynamically on
arbitrary code. Inodes are a easy way to uniquely identify files within our
execution, so our runtime virtualizes inodes by mapping them to unique
deterministic values, and I noticed inconsistencies from the results of
getdents, getdents64 vs stat.


On Wed, May 9, 2018 at 6:12 PM, Chris Lamb <lamby at debian.org> wrote:

> Hi Omar,
>
> > When using disorderfs the inodes returned by a system call to getdents
> are
> > all the same value
> […]
> > This leads to an inconsistent state between inodes as well as breaking
> > assumptions programs might make about unique inodes when checking the
> > results of getdents.
>
> Heh. How did you spot this? Or rather, what application/foo makes
> these assumptions?
>
> (Just curious. I mean, we use disorderfs a *lot* in the reproducible
> builds project and don't appear to have hit this before.)
>
>
> Best wishes,
>
> --
>       ,''`.
>      : :'  :     Chris Lamb
>      `. `'`      lamby at debian.org / chris-lamb.co.uk
>        `-
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/reproducible-builds/attachments/20180510/03edd324/attachment-0001.html>