Device mapper isolation method based on android containers

Abstract

The invention provides a device mapper isolation method based on android containers. The method includes the following step: S1, adding a chain table head dm_list for a mnt namespace structure in an operating system kernel, using the mnt_namespace structure to create a device mapper, and mounting the newly created device mapper on a chain table which takes the chain table head dm_list of a mnt_namespace as a head, wherein each mnt namespace has a device mapper chain table. The method has the advantages that the Device Mapper is a virtual driver of the kernel, thus incompatibility problems of different android machines do not exist, and the compatibility is improved.

Description

technical field [0001] The invention relates to an isolation method, in particular to an android container-based device mapper isolation method. Background technique [0002] With the development of android, a container-based multi-system solution has been proposed on android, which implements process isolation, file system isolation, network isolation and so on. The android container solution is based on the namespace (namespace) and cgroups technology provided by the linux kernel (operating system kernel), and multiple complete virtual spaces are isolated on a single kernel. [0003] In order to illustrate the latter mechanism, let's first talk about how the isolation of the file system is realized in the solution based on single-core multi-system. The isolation of the file system is achieved through chroot (Change Root, which is to change the location of the root directory referenced when the program is executed) and mnt namespace. Through chroot, a rootfs (root file sys...

AI Technical Summary

Problems solved by technology

The native Device mapper uses mount points to distinguish different Device mapper entities. Then in the solution based on single-core multi-system, it will appear that after the Device Mapper is successfully created through the / system mount point, the second system cannot use the same name. The problem of creating Device Mapper with the mount point

[0006] A feasible solution is to replace the file system that needs to use the Device Mapper mechanism in different systems with a different mount point, but this solution needs to modify a lot of code that uses the file system, and new services need to pay attention to this problem

Images