2021-12-03 11:16:59 +00:00
|
|
|
/* SPDX-License-Identifier: GPL-2.0 */
|
|
|
|
|
#ifndef _LINUX_MNT_IDMAPPING_H
|
|
|
|
|
#define _LINUX_MNT_IDMAPPING_H
|
|
|
|
|
|
|
|
|
|
#include <linux/types.h>
|
|
|
|
|
#include <linux/uidgid.h>
|
|
|
|
|
|
|
|
|
|
struct user_namespace;
|
fs: account for filesystem mappings
Currently we only support idmapped mounts for filesystems mounted
without an idmapping. This was a conscious decision mentioned in
multiple places (cf. e.g. [1]).
As explained at length in [3] it is perfectly fine to extend support for
idmapped mounts to filesystem's mounted with an idmapping should the
need arise. The need has been there for some time now. Various container
projects in userspace need this to run unprivileged and nested
unprivileged containers (cf. [2]).
Before we can port any filesystem that is mountable with an idmapping to
support idmapped mounts we need to first extend the mapping helpers to
account for the filesystem's idmapping. This again, is explained at
length in our documentation at [3] but I'll give an overview here again.
Currently, the low-level mapping helpers implement the remapping
algorithms described in [3] in a simplified manner. Because we could
rely on the fact that all filesystems supporting idmapped mounts are
mounted without an idmapping the translation step from or into the
filesystem idmapping could be skipped.
In order to support idmapped mounts of filesystem's mountable with an
idmapping the translation step we were able to skip before cannot be
skipped anymore. A filesystem mounted with an idmapping is very likely
to not use an identity mapping and will instead use a non-identity
mapping. So the translation step from or into the filesystem's idmapping
in the remapping algorithm cannot be skipped for such filesystems. More
details with examples can be found in [3].
This patch adds a few new and prepares some already existing low-level
mapping helpers to perform the full translation algorithm explained in
[3]. The low-level helpers can be written in a way that they only
perform the additional translation step when the filesystem is indeed
mounted with an idmapping.
If the low-level helpers detect that they are not dealing with an
idmapped mount they can simply return the relevant k{g,u}id unchanged;
no remapping needs to be performed at all. The no_idmapping() helper
detects whether the shortcut can be used.
If the low-level helpers detected that they are dealing with an idmapped
mount but the underlying filesystem is mounted without an idmapping we
can rely on the previous shorcut and can continue to skip the
translation step from or into the filesystem's idmapping.
These checks guarantee that only the minimal amount of work is
performed. As before, if idmapped mounts aren't used the low-level
helpers are idempotent and no work is performed at all.
This patch adds the helpers mapped_k{g,u}id_fs() and
mapped_k{g,u}id_user(). Following patches will port all places to
replace the old k{g,u}id_into_mnt() and k{g,u}id_from_mnt() with these
two new helpers. After the conversion is done k{g,u}id_into_mnt() and
k{g,u}id_from_mnt() will be removed. This also concludes the renaming of
the mapping helpers we started in [4]. Now, all mapping helpers will
started with the "mapped_" prefix making everything nice and consistent.
The mapped_k{g,u}id_fs() helpers replace the k{g,u}id_into_mnt()
helpers. They are to be used when k{g,u}ids are to be mapped from the
vfs, e.g. from from struct inode's i_{g,u}id. Conversely, the
mapped_k{g,u}id_user() helpers replace the k{g,u}id_from_mnt() helpers.
They are to be used when k{g,u}ids are to be written to disk, e.g. when
entering from a system call to change ownership of a file.
This patch only introduces the helpers. It doesn't yet convert the
relevant places to account for filesystem mounted with an idmapping.
[1]: commit 2ca4dcc4909d ("fs/mount_setattr: tighten permission checks")
[2]: https://github.com/containers/podman/issues/10374
[3]: Documentations/filesystems/idmappings.rst
[4]: commit a65e58e791a1 ("fs: document and rename fsid helpers")
Link: https://lore.kernel.org/r/20211123114227.3124056-5-brauner@kernel.org (v1)
Link: https://lore.kernel.org/r/20211130121032.3753852-5-brauner@kernel.org (v2)
Link: https://lore.kernel.org/r/20211203111707.3901969-5-brauner@kernel.org
Cc: Seth Forshee <sforshee@digitalocean.com>
Cc: Amir Goldstein <amir73il@gmail.com>
Cc: Christoph Hellwig <hch@lst.de>
Cc: Al Viro <viro@zeniv.linux.org.uk>
CC: linux-fsdevel@vger.kernel.org
Reviewed-by: Seth Forshee <sforshee@digitalocean.com>
Signed-off-by: Christian Brauner <christian.brauner@ubuntu.com>
2021-12-03 11:17:01 +00:00
|
|
|
/*
|
|
|
|
|
* Carries the initial idmapping of 0:0:4294967295 which is an identity
|
|
|
|
|
* mapping. This means that {g,u}id 0 is mapped to {g,u}id 0, {g,u}id 1 is
|
|
|
|
|
* mapped to {g,u}id 1, [...], {g,u}id 1000 to {g,u}id 1000, [...].
|
|
|
|
|
*/
|
2021-12-03 11:16:59 +00:00
|
|
|
extern struct user_namespace init_user_ns;
|
|
|
|
|
|
fs: account for filesystem mappings
Currently we only support idmapped mounts for filesystems mounted
without an idmapping. This was a conscious decision mentioned in
multiple places (cf. e.g. [1]).
As explained at length in [3] it is perfectly fine to extend support for
idmapped mounts to filesystem's mounted with an idmapping should the
need arise. The need has been there for some time now. Various container
projects in userspace need this to run unprivileged and nested
unprivileged containers (cf. [2]).
Before we can port any filesystem that is mountable with an idmapping to
support idmapped mounts we need to first extend the mapping helpers to
account for the filesystem's idmapping. This again, is explained at
length in our documentation at [3] but I'll give an overview here again.
Currently, the low-level mapping helpers implement the remapping
algorithms described in [3] in a simplified manner. Because we could
rely on the fact that all filesystems supporting idmapped mounts are
mounted without an idmapping the translation step from or into the
filesystem idmapping could be skipped.
In order to support idmapped mounts of filesystem's mountable with an
idmapping the translation step we were able to skip before cannot be
skipped anymore. A filesystem mounted with an idmapping is very likely
to not use an identity mapping and will instead use a non-identity
mapping. So the translation step from or into the filesystem's idmapping
in the remapping algorithm cannot be skipped for such filesystems. More
details with examples can be found in [3].
This patch adds a few new and prepares some already existing low-level
mapping helpers to perform the full translation algorithm explained in
[3]. The low-level helpers can be written in a way that they only
perform the additional translation step when the filesystem is indeed
mounted with an idmapping.
If the low-level helpers detect that they are not dealing with an
idmapped mount they can simply return the relevant k{g,u}id unchanged;
no remapping needs to be performed at all. The no_idmapping() helper
detects whether the shortcut can be used.
If the low-level helpers detected that they are dealing with an idmapped
mount but the underlying filesystem is mounted without an idmapping we
can rely on the previous shorcut and can continue to skip the
translation step from or into the filesystem's idmapping.
These checks guarantee that only the minimal amount of work is
performed. As before, if idmapped mounts aren't used the low-level
helpers are idempotent and no work is performed at all.
This patch adds the helpers mapped_k{g,u}id_fs() and
mapped_k{g,u}id_user(). Following patches will port all places to
replace the old k{g,u}id_into_mnt() and k{g,u}id_from_mnt() with these
two new helpers. After the conversion is done k{g,u}id_into_mnt() and
k{g,u}id_from_mnt() will be removed. This also concludes the renaming of
the mapping helpers we started in [4]. Now, all mapping helpers will
started with the "mapped_" prefix making everything nice and consistent.
The mapped_k{g,u}id_fs() helpers replace the k{g,u}id_into_mnt()
helpers. They are to be used when k{g,u}ids are to be mapped from the
vfs, e.g. from from struct inode's i_{g,u}id. Conversely, the
mapped_k{g,u}id_user() helpers replace the k{g,u}id_from_mnt() helpers.
They are to be used when k{g,u}ids are to be written to disk, e.g. when
entering from a system call to change ownership of a file.
This patch only introduces the helpers. It doesn't yet convert the
relevant places to account for filesystem mounted with an idmapping.
[1]: commit 2ca4dcc4909d ("fs/mount_setattr: tighten permission checks")
[2]: https://github.com/containers/podman/issues/10374
[3]: Documentations/filesystems/idmappings.rst
[4]: commit a65e58e791a1 ("fs: document and rename fsid helpers")
Link: https://lore.kernel.org/r/20211123114227.3124056-5-brauner@kernel.org (v1)
Link: https://lore.kernel.org/r/20211130121032.3753852-5-brauner@kernel.org (v2)
Link: https://lore.kernel.org/r/20211203111707.3901969-5-brauner@kernel.org
Cc: Seth Forshee <sforshee@digitalocean.com>
Cc: Amir Goldstein <amir73il@gmail.com>
Cc: Christoph Hellwig <hch@lst.de>
Cc: Al Viro <viro@zeniv.linux.org.uk>
CC: linux-fsdevel@vger.kernel.org
Reviewed-by: Seth Forshee <sforshee@digitalocean.com>
Signed-off-by: Christian Brauner <christian.brauner@ubuntu.com>
2021-12-03 11:17:01 +00:00
|
|
|
/**
|
|
|
|
|
* initial_idmapping - check whether this is the initial mapping
|
|
|
|
|
* @ns: idmapping to check
|
|
|
|
|
*
|
|
|
|
|
* Check whether this is the initial mapping, mapping 0 to 0, 1 to 1,
|
|
|
|
|
* [...], 1000 to 1000 [...].
|
|
|
|
|
*
|
|
|
|
|
* Return: true if this is the initial mapping, false if not.
|
|
|
|
|
*/
|
|
|
|
|
static inline bool initial_idmapping(const struct user_namespace *ns)
|
|
|
|
|
{
|
|
|
|
|
return ns == &init_user_ns;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* no_idmapping - check whether we can skip remapping a kuid/gid
|
|
|
|
|
* @mnt_userns: the mount's idmapping
|
|
|
|
|
* @fs_userns: the filesystem's idmapping
|
|
|
|
|
*
|
|
|
|
|
* This function can be used to check whether a remapping between two
|
|
|
|
|
* idmappings is required.
|
|
|
|
|
* An idmapped mount is a mount that has an idmapping attached to it that
|
|
|
|
|
* is different from the filsystem's idmapping and the initial idmapping.
|
|
|
|
|
* If the initial mapping is used or the idmapping of the mount and the
|
|
|
|
|
* filesystem are identical no remapping is required.
|
|
|
|
|
*
|
|
|
|
|
* Return: true if remapping can be skipped, false if not.
|
|
|
|
|
*/
|
|
|
|
|
static inline bool no_idmapping(const struct user_namespace *mnt_userns,
|
|
|
|
|
const struct user_namespace *fs_userns)
|
|
|
|
|
{
|
|
|
|
|
return initial_idmapping(mnt_userns) || mnt_userns == fs_userns;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* mapped_kuid_fs - map a filesystem kuid into a mnt_userns
|
|
|
|
|
* @mnt_userns: the mount's idmapping
|
|
|
|
|
* @fs_userns: the filesystem's idmapping
|
|
|
|
|
* @kuid : kuid to be mapped
|
|
|
|
|
*
|
|
|
|
|
* Take a @kuid and remap it from @fs_userns into @mnt_userns. Use this
|
|
|
|
|
* function when preparing a @kuid to be reported to userspace.
|
|
|
|
|
*
|
|
|
|
|
* If no_idmapping() determines that this is not an idmapped mount we can
|
|
|
|
|
* simply return @kuid unchanged.
|
|
|
|
|
* If initial_idmapping() tells us that the filesystem is not mounted with an
|
|
|
|
|
* idmapping we know the value of @kuid won't change when calling
|
|
|
|
|
* from_kuid() so we can simply retrieve the value via __kuid_val()
|
|
|
|
|
* directly.
|
|
|
|
|
*
|
|
|
|
|
* Return: @kuid mapped according to @mnt_userns.
|
|
|
|
|
* If @kuid has no mapping in either @mnt_userns or @fs_userns INVALID_UID is
|
|
|
|
|
* returned.
|
|
|
|
|
*/
|
|
|
|
|
static inline kuid_t mapped_kuid_fs(struct user_namespace *mnt_userns,
|
|
|
|
|
struct user_namespace *fs_userns,
|
|
|
|
|
kuid_t kuid)
|
|
|
|
|
{
|
|
|
|
|
uid_t uid;
|
|
|
|
|
|
|
|
|
|
if (no_idmapping(mnt_userns, fs_userns))
|
|
|
|
|
return kuid;
|
|
|
|
|
if (initial_idmapping(fs_userns))
|
|
|
|
|
uid = __kuid_val(kuid);
|
|
|
|
|
else
|
|
|
|
|
uid = from_kuid(fs_userns, kuid);
|
|
|
|
|
if (uid == (uid_t)-1)
|
|
|
|
|
return INVALID_UID;
|
|
|
|
|
return make_kuid(mnt_userns, uid);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* mapped_kgid_fs - map a filesystem kgid into a mnt_userns
|
|
|
|
|
* @mnt_userns: the mount's idmapping
|
|
|
|
|
* @fs_userns: the filesystem's idmapping
|
|
|
|
|
* @kgid : kgid to be mapped
|
|
|
|
|
*
|
|
|
|
|
* Take a @kgid and remap it from @fs_userns into @mnt_userns. Use this
|
|
|
|
|
* function when preparing a @kgid to be reported to userspace.
|
|
|
|
|
*
|
|
|
|
|
* If no_idmapping() determines that this is not an idmapped mount we can
|
|
|
|
|
* simply return @kgid unchanged.
|
|
|
|
|
* If initial_idmapping() tells us that the filesystem is not mounted with an
|
|
|
|
|
* idmapping we know the value of @kgid won't change when calling
|
|
|
|
|
* from_kgid() so we can simply retrieve the value via __kgid_val()
|
|
|
|
|
* directly.
|
|
|
|
|
*
|
|
|
|
|
* Return: @kgid mapped according to @mnt_userns.
|
|
|
|
|
* If @kgid has no mapping in either @mnt_userns or @fs_userns INVALID_GID is
|
|
|
|
|
* returned.
|
|
|
|
|
*/
|
|
|
|
|
static inline kgid_t mapped_kgid_fs(struct user_namespace *mnt_userns,
|
|
|
|
|
struct user_namespace *fs_userns,
|
|
|
|
|
kgid_t kgid)
|
|
|
|
|
{
|
|
|
|
|
gid_t gid;
|
|
|
|
|
|
|
|
|
|
if (no_idmapping(mnt_userns, fs_userns))
|
|
|
|
|
return kgid;
|
|
|
|
|
if (initial_idmapping(fs_userns))
|
|
|
|
|
gid = __kgid_val(kgid);
|
|
|
|
|
else
|
|
|
|
|
gid = from_kgid(fs_userns, kgid);
|
|
|
|
|
if (gid == (gid_t)-1)
|
|
|
|
|
return INVALID_GID;
|
|
|
|
|
return make_kgid(mnt_userns, gid);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* mapped_kuid_user - map a user kuid into a mnt_userns
|
|
|
|
|
* @mnt_userns: the mount's idmapping
|
|
|
|
|
* @fs_userns: the filesystem's idmapping
|
|
|
|
|
* @kuid : kuid to be mapped
|
|
|
|
|
*
|
|
|
|
|
* Use the idmapping of @mnt_userns to remap a @kuid into @fs_userns. Use this
|
|
|
|
|
* function when preparing a @kuid to be written to disk or inode.
|
|
|
|
|
*
|
|
|
|
|
* If no_idmapping() determines that this is not an idmapped mount we can
|
|
|
|
|
* simply return @kuid unchanged.
|
|
|
|
|
* If initial_idmapping() tells us that the filesystem is not mounted with an
|
|
|
|
|
* idmapping we know the value of @kuid won't change when calling
|
|
|
|
|
* make_kuid() so we can simply retrieve the value via KUIDT_INIT()
|
|
|
|
|
* directly.
|
|
|
|
|
*
|
|
|
|
|
* Return: @kuid mapped according to @mnt_userns.
|
|
|
|
|
* If @kuid has no mapping in either @mnt_userns or @fs_userns INVALID_UID is
|
|
|
|
|
* returned.
|
|
|
|
|
*/
|
|
|
|
|
static inline kuid_t mapped_kuid_user(struct user_namespace *mnt_userns,
|
|
|
|
|
struct user_namespace *fs_userns,
|
|
|
|
|
kuid_t kuid)
|
|
|
|
|
{
|
|
|
|
|
uid_t uid;
|
|
|
|
|
|
|
|
|
|
if (no_idmapping(mnt_userns, fs_userns))
|
|
|
|
|
return kuid;
|
|
|
|
|
uid = from_kuid(mnt_userns, kuid);
|
|
|
|
|
if (uid == (uid_t)-1)
|
|
|
|
|
return INVALID_UID;
|
|
|
|
|
if (initial_idmapping(fs_userns))
|
|
|
|
|
return KUIDT_INIT(uid);
|
|
|
|
|
return make_kuid(fs_userns, uid);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* mapped_kgid_user - map a user kgid into a mnt_userns
|
|
|
|
|
* @mnt_userns: the mount's idmapping
|
|
|
|
|
* @fs_userns: the filesystem's idmapping
|
|
|
|
|
* @kgid : kgid to be mapped
|
|
|
|
|
*
|
|
|
|
|
* Use the idmapping of @mnt_userns to remap a @kgid into @fs_userns. Use this
|
|
|
|
|
* function when preparing a @kgid to be written to disk or inode.
|
|
|
|
|
*
|
|
|
|
|
* If no_idmapping() determines that this is not an idmapped mount we can
|
|
|
|
|
* simply return @kgid unchanged.
|
|
|
|
|
* If initial_idmapping() tells us that the filesystem is not mounted with an
|
|
|
|
|
* idmapping we know the value of @kgid won't change when calling
|
|
|
|
|
* make_kgid() so we can simply retrieve the value via KGIDT_INIT()
|
|
|
|
|
* directly.
|
|
|
|
|
*
|
|
|
|
|
* Return: @kgid mapped according to @mnt_userns.
|
|
|
|
|
* If @kgid has no mapping in either @mnt_userns or @fs_userns INVALID_GID is
|
|
|
|
|
* returned.
|
|
|
|
|
*/
|
|
|
|
|
static inline kgid_t mapped_kgid_user(struct user_namespace *mnt_userns,
|
|
|
|
|
struct user_namespace *fs_userns,
|
|
|
|
|
kgid_t kgid)
|
|
|
|
|
{
|
|
|
|
|
gid_t gid;
|
|
|
|
|
|
|
|
|
|
if (no_idmapping(mnt_userns, fs_userns))
|
|
|
|
|
return kgid;
|
|
|
|
|
gid = from_kgid(mnt_userns, kgid);
|
|
|
|
|
if (gid == (gid_t)-1)
|
|
|
|
|
return INVALID_GID;
|
|
|
|
|
if (initial_idmapping(fs_userns))
|
|
|
|
|
return KGIDT_INIT(gid);
|
|
|
|
|
return make_kgid(fs_userns, gid);
|
|
|
|
|
}
|
|
|
|
|
|
2021-12-03 11:16:59 +00:00
|
|
|
/**
|
|
|
|
|
* mapped_fsuid - return caller's fsuid mapped up into a mnt_userns
|
fs: account for filesystem mappings
Currently we only support idmapped mounts for filesystems mounted
without an idmapping. This was a conscious decision mentioned in
multiple places (cf. e.g. [1]).
As explained at length in [3] it is perfectly fine to extend support for
idmapped mounts to filesystem's mounted with an idmapping should the
need arise. The need has been there for some time now. Various container
projects in userspace need this to run unprivileged and nested
unprivileged containers (cf. [2]).
Before we can port any filesystem that is mountable with an idmapping to
support idmapped mounts we need to first extend the mapping helpers to
account for the filesystem's idmapping. This again, is explained at
length in our documentation at [3] but I'll give an overview here again.
Currently, the low-level mapping helpers implement the remapping
algorithms described in [3] in a simplified manner. Because we could
rely on the fact that all filesystems supporting idmapped mounts are
mounted without an idmapping the translation step from or into the
filesystem idmapping could be skipped.
In order to support idmapped mounts of filesystem's mountable with an
idmapping the translation step we were able to skip before cannot be
skipped anymore. A filesystem mounted with an idmapping is very likely
to not use an identity mapping and will instead use a non-identity
mapping. So the translation step from or into the filesystem's idmapping
in the remapping algorithm cannot be skipped for such filesystems. More
details with examples can be found in [3].
This patch adds a few new and prepares some already existing low-level
mapping helpers to perform the full translation algorithm explained in
[3]. The low-level helpers can be written in a way that they only
perform the additional translation step when the filesystem is indeed
mounted with an idmapping.
If the low-level helpers detect that they are not dealing with an
idmapped mount they can simply return the relevant k{g,u}id unchanged;
no remapping needs to be performed at all. The no_idmapping() helper
detects whether the shortcut can be used.
If the low-level helpers detected that they are dealing with an idmapped
mount but the underlying filesystem is mounted without an idmapping we
can rely on the previous shorcut and can continue to skip the
translation step from or into the filesystem's idmapping.
These checks guarantee that only the minimal amount of work is
performed. As before, if idmapped mounts aren't used the low-level
helpers are idempotent and no work is performed at all.
This patch adds the helpers mapped_k{g,u}id_fs() and
mapped_k{g,u}id_user(). Following patches will port all places to
replace the old k{g,u}id_into_mnt() and k{g,u}id_from_mnt() with these
two new helpers. After the conversion is done k{g,u}id_into_mnt() and
k{g,u}id_from_mnt() will be removed. This also concludes the renaming of
the mapping helpers we started in [4]. Now, all mapping helpers will
started with the "mapped_" prefix making everything nice and consistent.
The mapped_k{g,u}id_fs() helpers replace the k{g,u}id_into_mnt()
helpers. They are to be used when k{g,u}ids are to be mapped from the
vfs, e.g. from from struct inode's i_{g,u}id. Conversely, the
mapped_k{g,u}id_user() helpers replace the k{g,u}id_from_mnt() helpers.
They are to be used when k{g,u}ids are to be written to disk, e.g. when
entering from a system call to change ownership of a file.
This patch only introduces the helpers. It doesn't yet convert the
relevant places to account for filesystem mounted with an idmapping.
[1]: commit 2ca4dcc4909d ("fs/mount_setattr: tighten permission checks")
[2]: https://github.com/containers/podman/issues/10374
[3]: Documentations/filesystems/idmappings.rst
[4]: commit a65e58e791a1 ("fs: document and rename fsid helpers")
Link: https://lore.kernel.org/r/20211123114227.3124056-5-brauner@kernel.org (v1)
Link: https://lore.kernel.org/r/20211130121032.3753852-5-brauner@kernel.org (v2)
Link: https://lore.kernel.org/r/20211203111707.3901969-5-brauner@kernel.org
Cc: Seth Forshee <sforshee@digitalocean.com>
Cc: Amir Goldstein <amir73il@gmail.com>
Cc: Christoph Hellwig <hch@lst.de>
Cc: Al Viro <viro@zeniv.linux.org.uk>
CC: linux-fsdevel@vger.kernel.org
Reviewed-by: Seth Forshee <sforshee@digitalocean.com>
Signed-off-by: Christian Brauner <christian.brauner@ubuntu.com>
2021-12-03 11:17:01 +00:00
|
|
|
* @mnt_userns: the mount's idmapping
|
2021-12-03 11:17:05 +00:00
|
|
|
* @fs_userns: the filesystem's idmapping
|
2021-12-03 11:16:59 +00:00
|
|
|
*
|
|
|
|
|
* Use this helper to initialize a new vfs or filesystem object based on
|
|
|
|
|
* the caller's fsuid. A common example is initializing the i_uid field of
|
|
|
|
|
* a newly allocated inode triggered by a creation event such as mkdir or
|
|
|
|
|
* O_CREAT. Other examples include the allocation of quotas for a specific
|
|
|
|
|
* user.
|
|
|
|
|
*
|
|
|
|
|
* Return: the caller's current fsuid mapped up according to @mnt_userns.
|
|
|
|
|
*/
|
2021-12-03 11:17:05 +00:00
|
|
|
static inline kuid_t mapped_fsuid(struct user_namespace *mnt_userns,
|
|
|
|
|
struct user_namespace *fs_userns)
|
2021-12-03 11:16:59 +00:00
|
|
|
{
|
2021-12-03 11:17:05 +00:00
|
|
|
return mapped_kuid_user(mnt_userns, fs_userns, current_fsuid());
|
2021-12-03 11:16:59 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* mapped_fsgid - return caller's fsgid mapped up into a mnt_userns
|
fs: account for filesystem mappings
Currently we only support idmapped mounts for filesystems mounted
without an idmapping. This was a conscious decision mentioned in
multiple places (cf. e.g. [1]).
As explained at length in [3] it is perfectly fine to extend support for
idmapped mounts to filesystem's mounted with an idmapping should the
need arise. The need has been there for some time now. Various container
projects in userspace need this to run unprivileged and nested
unprivileged containers (cf. [2]).
Before we can port any filesystem that is mountable with an idmapping to
support idmapped mounts we need to first extend the mapping helpers to
account for the filesystem's idmapping. This again, is explained at
length in our documentation at [3] but I'll give an overview here again.
Currently, the low-level mapping helpers implement the remapping
algorithms described in [3] in a simplified manner. Because we could
rely on the fact that all filesystems supporting idmapped mounts are
mounted without an idmapping the translation step from or into the
filesystem idmapping could be skipped.
In order to support idmapped mounts of filesystem's mountable with an
idmapping the translation step we were able to skip before cannot be
skipped anymore. A filesystem mounted with an idmapping is very likely
to not use an identity mapping and will instead use a non-identity
mapping. So the translation step from or into the filesystem's idmapping
in the remapping algorithm cannot be skipped for such filesystems. More
details with examples can be found in [3].
This patch adds a few new and prepares some already existing low-level
mapping helpers to perform the full translation algorithm explained in
[3]. The low-level helpers can be written in a way that they only
perform the additional translation step when the filesystem is indeed
mounted with an idmapping.
If the low-level helpers detect that they are not dealing with an
idmapped mount they can simply return the relevant k{g,u}id unchanged;
no remapping needs to be performed at all. The no_idmapping() helper
detects whether the shortcut can be used.
If the low-level helpers detected that they are dealing with an idmapped
mount but the underlying filesystem is mounted without an idmapping we
can rely on the previous shorcut and can continue to skip the
translation step from or into the filesystem's idmapping.
These checks guarantee that only the minimal amount of work is
performed. As before, if idmapped mounts aren't used the low-level
helpers are idempotent and no work is performed at all.
This patch adds the helpers mapped_k{g,u}id_fs() and
mapped_k{g,u}id_user(). Following patches will port all places to
replace the old k{g,u}id_into_mnt() and k{g,u}id_from_mnt() with these
two new helpers. After the conversion is done k{g,u}id_into_mnt() and
k{g,u}id_from_mnt() will be removed. This also concludes the renaming of
the mapping helpers we started in [4]. Now, all mapping helpers will
started with the "mapped_" prefix making everything nice and consistent.
The mapped_k{g,u}id_fs() helpers replace the k{g,u}id_into_mnt()
helpers. They are to be used when k{g,u}ids are to be mapped from the
vfs, e.g. from from struct inode's i_{g,u}id. Conversely, the
mapped_k{g,u}id_user() helpers replace the k{g,u}id_from_mnt() helpers.
They are to be used when k{g,u}ids are to be written to disk, e.g. when
entering from a system call to change ownership of a file.
This patch only introduces the helpers. It doesn't yet convert the
relevant places to account for filesystem mounted with an idmapping.
[1]: commit 2ca4dcc4909d ("fs/mount_setattr: tighten permission checks")
[2]: https://github.com/containers/podman/issues/10374
[3]: Documentations/filesystems/idmappings.rst
[4]: commit a65e58e791a1 ("fs: document and rename fsid helpers")
Link: https://lore.kernel.org/r/20211123114227.3124056-5-brauner@kernel.org (v1)
Link: https://lore.kernel.org/r/20211130121032.3753852-5-brauner@kernel.org (v2)
Link: https://lore.kernel.org/r/20211203111707.3901969-5-brauner@kernel.org
Cc: Seth Forshee <sforshee@digitalocean.com>
Cc: Amir Goldstein <amir73il@gmail.com>
Cc: Christoph Hellwig <hch@lst.de>
Cc: Al Viro <viro@zeniv.linux.org.uk>
CC: linux-fsdevel@vger.kernel.org
Reviewed-by: Seth Forshee <sforshee@digitalocean.com>
Signed-off-by: Christian Brauner <christian.brauner@ubuntu.com>
2021-12-03 11:17:01 +00:00
|
|
|
* @mnt_userns: the mount's idmapping
|
2021-12-03 11:17:05 +00:00
|
|
|
* @fs_userns: the filesystem's idmapping
|
2021-12-03 11:16:59 +00:00
|
|
|
*
|
|
|
|
|
* Use this helper to initialize a new vfs or filesystem object based on
|
|
|
|
|
* the caller's fsgid. A common example is initializing the i_gid field of
|
|
|
|
|
* a newly allocated inode triggered by a creation event such as mkdir or
|
|
|
|
|
* O_CREAT. Other examples include the allocation of quotas for a specific
|
|
|
|
|
* user.
|
|
|
|
|
*
|
|
|
|
|
* Return: the caller's current fsgid mapped up according to @mnt_userns.
|
|
|
|
|
*/
|
2021-12-03 11:17:05 +00:00
|
|
|
static inline kgid_t mapped_fsgid(struct user_namespace *mnt_userns,
|
|
|
|
|
struct user_namespace *fs_userns)
|
2021-12-03 11:16:59 +00:00
|
|
|
{
|
2021-12-03 11:17:05 +00:00
|
|
|
return mapped_kgid_user(mnt_userns, fs_userns, current_fsgid());
|
2021-12-03 11:16:59 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
#endif /* _LINUX_MNT_IDMAPPING_H */
|