Re: [patch 2/2] fs, proc: Introduce the /proc/<pid>/map_files/ directory v6

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

 



On 09/01/2011 06:58 PM, Tejun Heo wrote:
> On Thu, Sep 01, 2011 at 06:54:32PM -0700, Nicholas Miell wrote:
>> This doesn't seem to fully export all the information passed to mmap(2)
>> -- it encompasses the addr, size, fd and (assuming the generated
>> symlink's permissions are accurate) prot parameters, but does nothing to
>> export the flags or offset parameters.
> 
> It looks like,
> 
> /proc/*/fd : fdinfo ~= map_files : maps
> 

So are the filenames in /proc/$PID/map_files/ guaranteed to be identical
to the first field (first two fields? the part before the first space)
in /proc/$PID/maps?

When I open a file in /proc/$PID/map_files/, is offset 0 the start of
the file on disk or is it the first byte of the mapping?
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [Samba]     [Device Mapper]     [CEPH Development]
  Powered by Linux