diff options
author | Daan De Meyer <daan.j.demeyer@gmail.com> | 2022-09-23 09:55:26 +0200 |
---|---|---|
committer | Daan De Meyer <daan.j.demeyer@gmail.com> | 2022-09-23 09:55:26 +0200 |
commit | eaec6994947e876632a6032c0c2f5497ce408f09 (patch) | |
tree | d87bfa4ab3508a05c0f58763130f36940be2e7e3 /src/shared/mkfs-util.c | |
parent | eb43379cec13b69b5b0f6b9ff379b2e2c80ff18a (diff) | |
download | systemd-eaec6994947e876632a6032c0c2f5497ce408f09.tar.gz |
shared: Don't try to generate read-only filesystem that we don't support
We need explicit support to generate read-only filesystems, since we
always need to pass a source tree to the mkfs binary to populate the
filesystem. As such, let's add an explicit check to return a
recognizable error when users try to generate a read-only filesystem
that we don't support.
Diffstat (limited to 'src/shared/mkfs-util.c')
-rw-r--r-- | src/shared/mkfs-util.c | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/src/shared/mkfs-util.c b/src/shared/mkfs-util.c index c8e31aeb96..8161dbf825 100644 --- a/src/shared/mkfs-util.c +++ b/src/shared/mkfs-util.c @@ -123,6 +123,10 @@ int make_filesystem( return log_error_errno(SYNTHETIC_ERRNO(EPROTONOSUPPORT), "mksquashfs binary not available."); if (r < 0) return log_error_errno(r, "Failed to determine whether mksquashfs binary exists: %m"); + } else if (fstype_is_ro(fstype)) { + return log_error_errno(SYNTHETIC_ERRNO(EOPNOTSUPP), + "Don't know how to create read-only file system '%s', refusing.", + fstype); } else { if (root) return log_error_errno(SYNTHETIC_ERRNO(EOPNOTSUPP), |