[CRIU] [PATCH 2/2 v4] fsnotify: Always provide the path for inotify watchees

[Cyrill Gorcunov]

On Mon, Oct 19, 2015 at 03:13:43PM +0300, Pavel Emelyanov wrote:
> >>
> >> No, it's not about the kernel. Let's imagine the openat() fails with
> >> ENOENT. Can it? I guess it can, you try openat() in a loop. Now what
> >> if someone create _another_ file making the openat() that failed
> >> succeed. What you end up with? Wrong file opened by path.
> > 
> > Who is the "someone" who has created new file while we were on
> > the dumping frozen stage? :-)
> 
> This file could have been there _before_ we started migration and your
> openat() will open existing wrong file.

Seems I got what you mean. OK.