mirror of
https://github.com/hardkernel/linux.git
synced 2026-06-07 19:30:30 +09:00
Merge f30fabe78a ("Merge tag 'fs.idmapped.v5.19' of git://git.kernel.org/pub/scm/linux/kernel/git/brauner/linux") into android-mainline
Steps on the way to 5.19-rc1 Signed-off-by: Greg Kroah-Hartman <gregkh@google.com> Change-Id: I446d95b497c52867f9410bd7e85c049527caf0b4
This commit is contained in:
@@ -369,6 +369,11 @@ kernel maps the caller's userspace id down into a kernel id according to the
|
||||
caller's idmapping and then maps that kernel id up according to the
|
||||
filesystem's idmapping.
|
||||
|
||||
Let's see some examples with caller/filesystem idmapping but without mount
|
||||
idmappings. This will exhibit some problems we can hit. After that we will
|
||||
revisit/reconsider these examples, this time using mount idmappings, to see how
|
||||
they can solve the problems we observed before.
|
||||
|
||||
Example 1
|
||||
~~~~~~~~~
|
||||
|
||||
|
||||
@@ -4026,8 +4026,9 @@ static int can_idmap_mount(const struct mount_kattr *kattr, struct mount *mnt)
|
||||
static inline bool mnt_allow_writers(const struct mount_kattr *kattr,
|
||||
const struct mount *mnt)
|
||||
{
|
||||
return !(kattr->attr_set & MNT_READONLY) ||
|
||||
(mnt->mnt.mnt_flags & MNT_READONLY);
|
||||
return (!(kattr->attr_set & MNT_READONLY) ||
|
||||
(mnt->mnt.mnt_flags & MNT_READONLY)) &&
|
||||
!kattr->mnt_userns;
|
||||
}
|
||||
|
||||
static int mount_setattr_prepare(struct mount_kattr *kattr, struct mount *mnt)
|
||||
|
||||
Reference in New Issue
Block a user