GitLab

Several policies to select one among multiple writable branches.
See also the document in previous commit.
Signed-off-by: J. R. Okajima <hooanon05g@gmail.com>

Aufs can have multiple writable branches, and there are several
policies to select one among them.
This commit implements default "top-down-parent" for both of
creating-policy and copyup-policy.

See also the document in this commit.
Signed-off-by: J. R. Okajima <hooanon05g@gmail.com>

In freeing aufs iinfo objects, it acquires the internal rw_sem (see
another commit in detail). Since iinfo can be freed anytime, a deadlock
may happen due to the rw_sem. To prevent this problem, this commit
introduces a flag per task.
This is another (very) ugly approach which I don't like.
Signed-off-by: J. R. Okajima <hooanon05g@gmail.com>

Aufs pseudo-link (plink) represents a virtual hardlink across the
branches. To implement the plink maintenance mode, aufs uses procfs.
See also the document in this commit.

There is an external user-space utility called 'auplink' in
aufs-util.git, which has these features.
- 'list' shows the pseudo-linked inode numbers and filenames.
- 'cpup' copies-up all pseudo-link to the writable branch.
- 'flush' calls 'cpup', and then 'mount -o remount,clean_plink=inum'
Signed-off-by: J. R. Okajima <hooanon05g@gmail.com>

When user accesses aufs via other than fs related systemcalls, aufs
needs to identify which superblock is the target.  Here is the trick.
It is just a list of aufs superblocks.  Such way will be procfs and
MagicSysRq key.  For MagicSysRq support, see the later commit.
This is a dirty approach which I don't like, but I just don't have
another idea.
Signed-off-by: J. R. Okajima <hooanon05g@gmail.com>

As mentioned earlier, sometimes the size of XINO file is a problem.
Aufs has a feature to truncate it asynchronously using workqueue. But it
may not be so effective in some cases, and you may want to stop
discontiguous distribution of the inode numbers on branch fs.
See also the log in another commit.
Signed-off-by: J. R. Okajima <hooanon05g@gmail.com>

The branch path can be much longer and it is not suitable to print via
/proc/mounts as a part of mount options. Aufs can show it either
separately via sysfs or /proc/mounts (as a part of mount options).
This approach affects the lifetime of aufs objects and sbinfo contains
kobject (in another commit). Theoretically user can disable
CONFIG_SYSFS, but the lifetime management is always necessary. So
supporting sysfs is split into two files, sysaufs.c and sysfs.c.
sysaufs.c is always compiled, but sysfs.c is compiled only when
CONFIG_SYSFS is enabled.
Signed-off-by: J. R. Okajima <hooanon05g@gmail.com>

XINO and XIB files are to maintain the inode numbers in aufs
(cf. struct.txt and aufs manual in aufs-util.git).

XINO file contains just a sequence of the inode numbers, and their
offset in the file is real_inum x sizeof(inum).  So the size is limited
by s_maxbytes of the filesystem where XINO file is located.  In order to
support the larger inum, aufs stores XINO files as an internal array.

Sometimes the size of XINO file can be a problem, ie. too big,
particularly when XINO files are located on tmpfs. In this case, another
separate patch tmpfs-ino.patch in aufs4-standalone.git is recommended
(as well as vfs-ino.patch). The patch makes tmpfs to maintain inode
number within itself and suppress its discontiguous distribution.

See also the document in next commit.
Signed-off-by: J. R. Okajima <hooanon05g@gmail.com>

Aufs uses the workqueue both synchronously and asynchronously.
For sync-use-case, aufs uses its own specific wkq since doesn't want to
be disturbed by other tasks on the system. For async-use-case, aufs uses
the system global workqueue.
Aufs has to prevent itself to being unmounted during the async-task is
queued.

See also the document in this commit.
Signed-off-by: J. R. Okajima <hooanon05g@gmail.com>

For details, see previous commit.
Signed-off-by: J. R. Okajima <hooanon05g@gmail.com>

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: J. R. Okajima <hooanon05g@gmail.com>

The generation of iinfo and dinfo inherit sbinfo's.
Also iinfo generation tracks the branch inode's generation to test the
matching after the branch management.
Signed-off-by: J. R. Okajima <hooanon05g@gmail.com>

The structure is very similar to inode and dentry infos (in previous
commits), but the internal array is for 'struct au_branch' instead of
'superblock.' Additionally the lifetime of 'struct au_sbinfo' is managed
by kobject since it will be connected to sysfs by later commit.
Signed-off-by: J. R. Okajima <hooanon05g@gmail.com>

The structure is very similar to aufs inode info (in previous commit).
Signed-off-by: J. R. Okajima <hooanon05g@gmail.com>

See the documents in this commit.
Signed-off-by: J. R. Okajima <hooanon05g@gmail.com>