All Virtuozzo development lists (kernel + QEMU)
 help / color / mirror / Atom feed
From: Konstantin Khorenko <khorenko@virtuozzo.com>
To: Eva Kurchatova <eva.kurchatova@virtuozzo.com>
Cc: devel@openvz.org
Subject: Re: [Devel] [PATCH hci-8.1] ve/fs: let a container mount ext2 and ext3 through the ext4 driver
Date: Thu, 22 Oct 2026 18:44:01 +0200	[thread overview]
Message-ID: <b0fd8086-77fa-40c5-83c6-d956423ded03@virtuozzo.com> (raw)
In-Reply-To: <20261021180310.2341467-1-eva.kurchatova@virtuozzo.com>

On 10/21/26 20:03, Eva Kurchatova wrote:
> The ext4 driver also registers the ext2 and ext3 filesystem types, and
> those two carry none of the container flags ext4 itself has, so inside
> a container they are absent from /proc/filesystems and a mount of an
> ext2 or ext3 image fails with "unknown filesystem type", while the same
> image mounts as ext4. It is the same code either way, so give the two
> aliases the same flags; LTP formats its test devices as ext2 by default
> and every one of those tests breaks in a container on that mount.

i do not see any reason to enable mounting ext2/ext3 filesystems inside
Containers while we already allow ext4 mounts.

We do support ext4 inside a CT and we test it.
We do not test ext2/ext3 - why to allow it?

Until we have a proper usecase / a request from a customer, i would not enable it.

If we are talking about LTP tests, we can run currently failing tests inside a CT
with LTP_DEV_FS_TYPE=... set

> 
> https://virtuozzo.atlassian.net/browse/VSTOR-132330
> Feature: fs: whiltelist what can be mounted in a CT
> 
> Signed-off-by: Eva Kurchatova <eva.kurchatova@virtuozzo.com>
> ---
>  fs/ext4/super.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/fs/ext4/super.c b/fs/ext4/super.c
> index e292c0597eaf..0f73473e2d4d 100644
> --- a/fs/ext4/super.c
> +++ b/fs/ext4/super.c
> @@ -137,7 +137,7 @@ static struct file_system_type ext2_fs_type = {
>  	.init_fs_context	= ext4_init_fs_context,
>  	.parameters		= ext4_param_specs,
>  	.kill_sb		= ext4_kill_sb,
> -	.fs_flags		= FS_REQUIRES_DEV,
> +	.fs_flags		= FS_REQUIRES_DEV | FS_VIRTUALIZED | FS_VE_MOUNT,
>  };
>  MODULE_ALIAS_FS("ext2");
>  MODULE_ALIAS("ext2");
> @@ -153,7 +153,7 @@ static struct file_system_type ext3_fs_type = {
>  	.init_fs_context	= ext4_init_fs_context,
>  	.parameters		= ext4_param_specs,
>  	.kill_sb		= ext4_kill_sb,
> -	.fs_flags		= FS_REQUIRES_DEV,
> +	.fs_flags		= FS_REQUIRES_DEV | FS_VIRTUALIZED | FS_VE_MOUNT,
>  };
>  MODULE_ALIAS_FS("ext3");
>  MODULE_ALIAS("ext3");

_______________________________________________
Devel mailing list
Devel@openvz.org
https://lists.openvz.org/mailman/listinfo/devel

      parent reply	other threads:[~2026-10-22 16:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-21 18:03 Eva Kurchatova
2026-10-21 18:07 ` no-reply
2026-10-22 16:44 ` Konstantin Khorenko [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b0fd8086-77fa-40c5-83c6-d956423ded03@virtuozzo.com \
    --to=khorenko@virtuozzo.com \
    --cc=devel@openvz.org \
    --cc=eva.kurchatova@virtuozzo.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.