From: Gao Xiang <xiang@kernel.org>
To: Naoto Yamaguchi <wata2ki@gmail.com>
Cc: Naoto Yamaguchi <naoto.yamaguchi@aisin.co.jp>,
linux-erofs@lists.ozlabs.org
Subject: Re: [PATCH] erofs-utils: mkfs: Add volume-name setting support
Date: Wed, 5 Oct 2022 00:15:53 +0800 [thread overview]
Message-ID: <YzxcOcJK+8gB8psP@debian> (raw)
In-Reply-To: <20221004160237.10849-1-naoto.yamaguchi@aisin.co.jp>
Hi Naoto,
On Wed, Oct 05, 2022 at 01:02:37AM +0900, Naoto Yamaguchi wrote:
> The erofs_super_block has volume_name field. On the other hand,
> mkfs.erofs is not supporting to set volume name.
> This patch add volume-name setting support to mkfs.erofs.
> Option keyword is similar to mkfs.vfat.
>
> usage:
> mkfs.erofs -n volume-name image-fn dir
Thanks for your patch! The patch itself generally looks good to me.
Just two minor ideas:
1) How about following mke2fs by using "-L volume-label" ?
https://www.man7.org/linux/man-pages/man8/mke2fs.8.html
2) If possible, how about adding a kernel ioctl for this if you have
more interest? I mean FS_IOC_GETFSLABEL.
>
> Signed-off-by: Naoto Yamaguchi <naoto.yamaguchi@aisin.co.jp>
> ---
> include/erofs/internal.h | 1 +
> man/mkfs.erofs.1 | 4 ++++
> mkfs/main.c | 13 ++++++++++++-
> 3 files changed, 17 insertions(+), 1 deletion(-)
>
> diff --git a/include/erofs/internal.h b/include/erofs/internal.h
> index 2e0aae8..7dc42eb 100644
> --- a/include/erofs/internal.h
> +++ b/include/erofs/internal.h
> @@ -92,6 +92,7 @@ struct erofs_sb_info {
> u64 inos;
>
> u8 uuid[16];
> + char volume_name[16];
>
> u16 available_compr_algs;
> u16 lz4_max_distance;
> diff --git a/man/mkfs.erofs.1 b/man/mkfs.erofs.1
> index 11e8323..fb98505 100644
> --- a/man/mkfs.erofs.1
> +++ b/man/mkfs.erofs.1
> @@ -32,6 +32,10 @@ big pcluster feature if needed (Linux v5.13+).
> Specify the level of debugging messages. The default is 2, which shows basic
> warning messages.
> .TP
> +.BI "\-n " volume-name
> +Set the volume name for the filesystem to volume-name. The maximum length of
> +the volume name is 16 bytes.
> +.TP
> .BI "\-x " #
> Specify the upper limit of an xattr which is still inlined. The default is 2.
> Disable storing xattrs if < 0.
> diff --git a/mkfs/main.c b/mkfs/main.c
> index 594ecf9..613ee46 100644
> --- a/mkfs/main.c
> +++ b/mkfs/main.c
> @@ -80,6 +80,7 @@ static void usage(void)
> fputs("usage: [options] FILE DIRECTORY\n\n"
> "Generate erofs image from DIRECTORY to FILE, and [options] are:\n"
> " -d# set output message level to # (maximum 9)\n"
> + " -n volume-name set the volume name (max 16 bytes).\n"
...
> " -x# set xattr tolerance to # (< 0, disable xattrs; default 2)\n"
> " -zX[,Y] X=compressor (Y=compression level, optional)\n"
> " -C# specify the size of compress physical cluster in bytes\n"
" -L volume-label set the volume label (maximum 12)\n"
Thanks,
Gao Xiang
next prev parent reply other threads:[~2022-10-04 16:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-04 16:02 [PATCH] erofs-utils: mkfs: Add volume-name setting support Naoto Yamaguchi
2022-10-04 16:15 ` Gao Xiang [this message]
2022-10-04 16:25 ` Naoto Yamaguchi
2022-10-04 16:33 ` Gao Xiang
2022-10-04 16:43 ` Naoto Yamaguchi
2022-10-04 16:49 ` Gao Xiang
2022-10-04 17:01 ` [PATCH v3] " Naoto Yamaguchi
2022-10-04 17:04 ` [PATCH] " Naoto Yamaguchi
2022-10-04 17:54 ` Gao Xiang
2022-10-04 21:33 ` Naoto Yamaguchi
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=YzxcOcJK+8gB8psP@debian \
--to=xiang@kernel.org \
--cc=linux-erofs@lists.ozlabs.org \
--cc=naoto.yamaguchi@aisin.co.jp \
--cc=wata2ki@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox