Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] fs/f2fs: add support for creating a f2fs image
Date: Sat, 3 Nov 2018 15:48:43 +0100	[thread overview]
Message-ID: <20181103154843.761e9e07@windsurf> (raw)
In-Reply-To: <20181026200016.30856-3-grzegorz@blach.pl>

Hello,

On Fri, 26 Oct 2018 22:00:16 +0200, Grzegorz Blach wrote:
> This patch makes possible to create rootfs image using f2fs filesystem.
> 
> Signed-off-by: Grzegorz Blach <grzegorz@blach.pl>

I have applied, after doing a number of changes, mainly splitting into
separate patches, as suggested by Yann E. Morin.

However, now that you have added F2FS support, it would be good if you
could add a test in our test suite for this filesystem. Look at
support/testing/tests/fs/ for the other filesystem tests that we have.
Could you add something like this ?

> +config BR2_TARGET_ROOTFS_F2FS_COLD_FILES
> +	string "extension list for cold files"

Any reason for having added this option for cold files, but not the
symmetric option for hot files ?

> +	help
> +	  Specify a file extension list in order f2fs to treat them
> +	  as cold files. The default list includes most of multimedia
> +	  file extensions such as jpg, gif, mpeg, mkv, and so on.

I've seen this after committing, but the help text of mkfs.f2fs seems
to imply that the list of extensions should be comma separated. If
that's the case, it should be mentioned in the help text, because most
Buildroot options use space-separated lists, not comma-separated ones.

> +config BR2_TARGET_ROOTFS_F2FS_OVERPROVISION
> +	int "size for overprovision area (0 for auto calculation)"

Actually 0 is not auto-calculation. 0 will not pass any -O option, and
therefore mkfs.f2fs will use its default of 5%.

Also, this option doesn't give the size, but the ratio.

I've fixed both aspects when committing.

> +	dd if=/dev/zero of=$@ bs=1 count=0 seek=$(F2FS_SIZE)

I've replaced by a truncate, as suggested by Yann.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  parent reply	other threads:[~2018-11-03 14:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-26 20:00 [Buildroot] [PATCH 0/2] Creating a sparse file in ROOTFS_F2FS_CMD Grzegorz Blach
2018-10-26 20:00 ` [Buildroot] [PATCH 1/2] package/f2fs-tools: add host package Grzegorz Blach
2018-10-31 21:21   ` Yann E. MORIN
2018-11-03 14:45     ` Thomas Petazzoni
2018-11-03 14:37   ` Thomas Petazzoni
2018-10-26 20:00 ` [Buildroot] [PATCH 2/2] fs/f2fs: add support for creating a f2fs image Grzegorz Blach
2018-10-31 21:42   ` Yann E. MORIN
2018-11-03 14:48   ` Thomas Petazzoni [this message]
2018-11-04 16:48     ` Grzegorz Blach

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=20181103154843.761e9e07@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@busybox.net \
    /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