pool/util-linux
SHA256
12
0
Fork 3
Code Issues Pull Requests Activity

- Enable mountfd support again (jsc#PED-9752).

Browse Source 
BREAKING CHANGE
  Mountfd is nearly completely compatible with the old mount. There
  is a special case that cannot be handled by mountfd, and it needs
  to be handled by applications:
  Mountfd discriminates between physical mount layer and virtual
  mount layer. Once the physical mount layer is read-only,
  read-write mount on the virtual layer is not possible.
  If the first mount is read only, then the physical filesystem is
  mounted read-only, and later mount of the same file system as
  read-write is not possible. To solve this problem, the first
  mount needs to be read-only only on the virtual layer, keeping
  the physical layer read-write.
  The user space fix is simple:
  Instead of
    mount -oro
  use
    mount -oro=vfs
  This will keep the physical layer read-write, but the virtual
  file system layer (and the user space access) will be read-only.

OBS-URL: https://build.opensuse.org/package/show/Base:System/util-linux?expand=0&rev=589
This commit is contained in:
Stanislav Brabec
2025-04-25 10:12:33 +00:00
committed by Git OBS Bridge
parent 85211d2fa9
commit f93ce2303c
2 changed files with 24 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

24
util-linux.changes
View File

@@ -1,3 +1,27 @@
-------------------------------------------------------------------
Thu Apr 17 18:33:03 UTC 2025 - Stanislav Brabec <sbrabec@suse.com>
- Enable mountfd support again (jsc#PED-9752).
BREAKING CHANGE
Mountfd is nearly completely compatible with the old mount. There
is a special case that cannot be handled by mountfd, and it needs
to be handled by applications:
Mountfd discriminates between physical mount layer and virtual
mount layer. Once the physical mount layer is read-only,
read-write mount on the virtual layer is not possible.
If the first mount is read only, then the physical filesystem is
mounted read-only, and later mount of the same file system as
read-write is not possible. To solve this problem, the first
mount needs to be read-only only on the virtual layer, keeping
the physical layer read-write.
The user space fix is simple:
Instead of
mount -oro
use
mount -oro=vfs
This will keep the physical layer read-write, but the virtual
file system layer (and the user space access) will be read-only.
-------------------------------------------------------------------
Mon Apr 7 21:00:58 UTC 2025 - Stanislav Brabec <sbrabec@suse.com>

1
util-linux.spec
View File

@@ -561,7 +561,6 @@ configure_options="$configure_options --with-systemd "
--enable-fs-paths-default="/sbin:/usr/sbin"\
--enable-static\
--with-vendordir=%{_distconfdir}\
--disable-libmount-mountfd-support\
$configure_options
%make_build
}