diff options
| author | Linus Torvalds <torvalds@linux-foundation.org> | 2021-05-19 18:12:31 +0200 |
|---|---|---|
| committer | Linus Torvalds <torvalds@linux-foundation.org> | 2021-05-19 18:12:31 +0200 |
| commit | c3d0e3fd41b7f0f5d5d5b6022ab7e813f04ea727 (patch) | |
| tree | 49d7ae853af8dae021d8b906aaf5b762ef6aa42e /arch/arm | |
| parent | Revert "i915: fix remap_io_sg to verify the pgprot" (diff) | |
| parent | fs/mount_setattr: tighten permission checks (diff) | |
| download | linux-c3d0e3fd41b7f0f5d5d5b6022ab7e813f04ea727.tar.xz linux-c3d0e3fd41b7f0f5d5d5b6022ab7e813f04ea727.zip | |
Merge tag 'fs.idmapped.mount_setattr.v5.13-rc3' of gitolite.kernel.org:pub/scm/linux/kernel/git/brauner/linux
Pull mount_setattr fix from Christian Brauner:
"This makes an underlying idmapping assumption more explicit.
We currently don't have any filesystems that support idmapped mounts
which are mountable inside a user namespace, i.e. where s_user_ns !=
init_user_ns. That was a deliberate decision for now as userns root
can just mount the filesystem themselves.
Express this restriction explicitly and enforce it until there's a
real use-case for this. This way we can notice it and will have a
chance to adapt and audit our translation helpers and fstests
appropriately if we need to support such filesystems"
* tag 'fs.idmapped.mount_setattr.v5.13-rc3' of gitolite.kernel.org:pub/scm/linux/kernel/git/brauner/linux:
fs/mount_setattr: tighten permission checks
Diffstat (limited to 'arch/arm')
0 files changed, 0 insertions, 0 deletions