Re: procfs reports unexpected mnt_id and path for overlayfs files

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Jul 6, 2015 at 7:45 PM, Saied Kazemi <saied@xxxxxxxxxx> wrote:
> On Wed, Apr 15, 2015 at 8:07 AM, Miklos Szeredi <miklos@xxxxxxxxxx> wrote:
>> On Wed, Apr 15, 2015 at 10:50 AM, Andrew Vagin <avagin@xxxxxxxx> wrote:
>>> Hello Miklos and Everyone else,
>>>
>>> We have a report that a container with overlayfs can't be checkpointed.
>>>
>>> To dump file descriptors we get information from /proc/pid/fd/ and /proc/pid/fdinfo.
>>>
>>> But in case of overlayfs we see unexpected values there.
>>>
>>> /proc/PID/fdinfo/FD contains mnt_id which isn't presented in /proc/pid/mountinfo.
>>> /proc/PID/fd/FD does not contain an absolute path to the opened file.
>>>
>>> Can someone help to fix these issues?
>>
>> See this:
>>
>> https://lkml.org/lkml/2015/3/20/372
>>
>> Al didn't like that patch.  But it definitely will be fixed, one way
>> or the other, in the near future.

Should be fixed in 4.2.

Thanks,
Miklos
--
To unsubscribe from this list: send the line "unsubscribe linux-unionfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux Filesystems Devel]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux