[lkml]   [2010]   [Jun]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [rfc] new stat*fs-like syscall?
    On Thu, 24 Jun 2010, Andy Lutomirski wrote:
    > Something like fsid but actually specified to uniquely identify a
    > superblock. (Currently, fsid seems to be set by the filesystem, and
    > nothing in particular ensures that two different filesystems couldn't
    > have collisions.) We could guarantee (or have a flag guaranteeing) that
    > (fsid, st_inode) actually uniquely identifies an inode.
    > Similarly, something like fsid that uniquely identifies the vfsmount
    > could be useful, although I don't know how easy that would be to provide
    > for fstat?fs.
    > If we could expose the complete set of filesystem mount options so that
    > mount(1) didn't have to look at /proc/self/mounts or /etc/mtab, then
    > playing with chroots would be that much easier.
    > Should we expose superblock and vfsmount options separately? We have
    > read-only bind mounts now, but the way they work is rather inscrutable,
    > and if stat?fs could say "superblock is read-write but vfsmount is
    > readonly" then people might be able to make more sense of what's going on.

    You'll find all of those things in /proc/self/mountinfo.


     \ /
      Last update: 2010-06-24 16:21    [W:0.020 / U:98.836 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site