1. 09 Mar, 2019 7 commits
    • J. R. Okajima's avatar
      aufs: inode op, add, link · 39391364
      J. R. Okajima authored
      
      
      Implement i_op->link().
      As aufs supports 'pseudo-link', aufs_link() can make it without
      copying-up. In the case of aufs_link() has to copy-up, the name of the
      target file is used as-is, and it is pseudo-linked. In other words,
      calling link(2) after the copy-up is unnecessary.
      
      See also struct.txt in previous commit.
      Signed-off-by: default avatarJ. R. Okajima <hooanon05g@gmail.com>
      39391364
    • J. R. Okajima's avatar
      aufs: inode op, lookup · ed4978f6
      J. R. Okajima authored
      
      
      Implement dir.i_op->lookup() and ->permission().
      Signed-off-by: default avatarJ. R. Okajima <hooanon05g@gmail.com>
      ed4978f6
    • J. R. Okajima's avatar
      aufs: remount 4/5, refresh the internal branch array · fb70a624
      J. R. Okajima authored
      
      
      Maintain the internal array including corresponding XINO file and sysfs
      entries.
      Signed-off-by: default avatarJ. R. Okajima <hooanon05g@gmail.com>
      fb70a624
    • J. R. Okajima's avatar
      aufs: hnotify 2/3, body · 6b81a214
      J. R. Okajima authored
      
      
      The feature is constructed by two layers. One is generic interface, and
      the other is exact implementation. This is rather historical. Originally
      aufs implemented this feature based upon 'inotify.' Later 'fsnotify'
      made 'inotify' obsolete. During the transition period, these two layers
      were introduced to support both of 'inotify' and 'fsnotify.' Currently
      only 'fsnotify' is supported, but the layers are kept for the future
      use.
      
      This feature is compiled only when CONFIG_AUFS_HNOTIFY is enabled.
      See also the document in previous commit.
      Signed-off-by: default avatarJ. R. Okajima <hooanon05g@gmail.com>
      6b81a214
    • J. R. Okajima's avatar
      aufs: readonly branch 1/2, definition · b7051459
      J. R. Okajima authored
      
      
      The branch object is managed by the sbinfo object as an element of its
      internal array. The iinfo and dinfo objects contain the branch id, and
      it will be used to implement the correct order in branch management
      (add/del).
      
      See also the documents in this commit.
      Signed-off-by: default avatarJ. R. Okajima <hooanon05g@gmail.com>
      b7051459
    • J. R. Okajima's avatar
      aufs: infos generation 1/2, dcsub · fa25dbe6
      J. R. Okajima authored
      
      
      The generation of aufs objects will be updated by the branch
      management (add/del branches, by later commit), and aufs will refresh
      the objects based upon the generation.
      In refreshing dinfos, aufs will find all ancestors of the given dentry
      and store the pointers in dynamically allocated memory. I don't think it
      beautiful, but I don't have any other idea.
      Signed-off-by: default avatarJ. R. Okajima <hooanon05g@gmail.com>
      fa25dbe6
    • J. R. Okajima's avatar
      aufs: dinfo core · ee166183
      J. R. Okajima authored
      
      
      The structure is very similar to aufs inode info (in previous commit).
      Signed-off-by: default avatarJ. R. Okajima <hooanon05g@gmail.com>
      ee166183