diff options
| author | Al Viro <[email protected]> | 2025-08-14 05:44:31 +0000 |
|---|---|---|
| committer | Al Viro <[email protected]> | 2025-08-19 16:03:23 +0000 |
| commit | cffd0441872e7f6b1fce5e78fb1c99187a291330 (patch) | |
| tree | c2bc5a2a2cd6999a09bf947b623f43ce0ea42759 /drivers/net/ethernet/intel/igc/igc_main.c | |
| parent | propagate_umount(): only surviving overmounts should be reparented (diff) | |
| download | kernel-cffd0441872e7f6b1fce5e78fb1c99187a291330.tar.gz kernel-cffd0441872e7f6b1fce5e78fb1c99187a291330.zip | |
use uniform permission checks for all mount propagation changes
do_change_type() and do_set_group() are operating on different
aspects of the same thing - propagation graph. The latter
asks for mounts involved to be mounted in namespace(s) the caller
has CAP_SYS_ADMIN for. The former is a mess - originally it
didn't even check that mount *is* mounted. That got fixed,
but the resulting check turns out to be too strict for userland -
in effect, we check that mount is in our namespace, having already
checked that we have CAP_SYS_ADMIN there.
What we really need (in both cases) is
* only touch mounts that are mounted. That's a must-have
constraint - data corruption happens if it get violated.
* don't allow to mess with a namespace unless you already
have enough permissions to do so (i.e. CAP_SYS_ADMIN in its userns).
That's an equivalent of what do_set_group() does; let's extract that
into a helper (may_change_propagation()) and use it in both
do_set_group() and do_change_type().
Fixes: 12f147ddd6de "do_change_type(): refuse to operate on unmounted/not ours mounts"
Acked-by: Andrei Vagin <[email protected]>
Reviewed-by: Pavel Tikhomirov <[email protected]>
Tested-by: Pavel Tikhomirov <[email protected]>
Reviewed-by: Christian Brauner <[email protected]>
Signed-off-by: Al Viro <[email protected]>
Diffstat (limited to 'drivers/net/ethernet/intel/igc/igc_main.c')
0 files changed, 0 insertions, 0 deletions
