public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Luca Di Maio <luca.dimaio1@gmail.com>
Cc: linux-xfs@vger.kernel.org, dimitri.ledkov@chainguard.dev,
	smoser@chainguard.dev, hch@infradead.org
Subject: Re: [PATCH v6 0/4] mkfs: add ability to populate filesystem from directory
Date: Wed, 23 Apr 2025 13:03:14 -0700	[thread overview]
Message-ID: <20250423200314.GG25675@frogsfrogsfrogs> (raw)
In-Reply-To: <20250423160319.810025-1-luca.dimaio1@gmail.com>

On Wed, Apr 23, 2025 at 06:03:15PM +0200, Luca Di Maio wrote:
> Currently the only way to pre populate an XFS partition is via the
> prototype file. While it works it has some limitations like:
>   - not allowed spaces in file names
>   - not preserving timestamps of original inodes
> 
> This series adds a new -P option to mkfs.xfs that allows users to
> populate a newly created filesystem directly from an existing directory.
> While similar to the prototype functionality, this doesn't require
> writing a prototype file.
> The implementation preserves file and directory attributes (ownership,
> permissions, timestamps) from the source directory when copying content
> to the new filesystem.
> 
> [v1] -> [v2]
>   remove changes to protofile spec
>   ensure backward compatibility
> [v2] -> [v3]
>   use inode_set_[acm]time() as suggested
>   avoid copying atime and ctime
>   they are often problematic for reproducibility, and
>   mtime is the important information to preserve anyway
> [v3] -> [v4]
>   rewrite functionality to populate directly from an input directory
>   this is similar to mkfs.ext4 option.
> [v4] -> [v5]
>   reorder patch to make it easier to review
>   reflow to keep code below 80 chars
>   use _() macro in prints
>   add SPDX headers to new files
>   fix comment styling
>   move from typedef to structs
>   move direntry handling to own function
> [v5] -> [v6]
>   rebase on 6.14

Urrrk, one revision per day, please.

--D

> Luca Di Maio (4):
>   proto: expose more functions from proto
>   populate: add ability to populate a filesystem from a directory
>   mkfs: add -P flag to populate a filesystem from a directory
>   man: document -P flag to populate a filesystem from a directory
> 
>  man/man8/mkfs.xfs.8.in |   7 +
>  mkfs/Makefile          |   2 +-
>  mkfs/populate.c        | 313 +++++++++++++++++++++++++++++++++++++++++
>  mkfs/populate.h        |  10 ++
>  mkfs/proto.c           |  33 ++---
>  mkfs/proto.h           |  22 +++
>  mkfs/xfs_mkfs.c        |  23 ++-
>  7 files changed, 385 insertions(+), 25 deletions(-)
>  create mode 100644 mkfs/populate.c
>  create mode 100644 mkfs/populate.h
> 
> Signed-off-by: Luca Di Maio <luca.dimaio1@gmail.com>
> 
> --
> 2.49.0
> 

      parent reply	other threads:[~2025-04-23 20:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-23 16:03 [PATCH v6 0/4] mkfs: add ability to populate filesystem from directory Luca Di Maio
2025-04-23 16:03 ` [PATCH v6 1/4] proto: expose more functions from proto Luca Di Maio
2025-04-23 16:03 ` [PATCH v6 2/4] populate: add ability to populate a filesystem from a directory Luca Di Maio
2025-04-23 20:23   ` Darrick J. Wong
2025-04-24 16:09     ` Luca Di Maio
2025-04-24 22:00       ` Darrick J. Wong
2025-04-25 13:10         ` Christoph Hellwig
2025-04-25 15:00           ` Darrick J. Wong
2025-04-25 17:58             ` Luca Di Maio
2025-04-23 16:03 ` [PATCH v6 3/4] mkfs: add -P flag " Luca Di Maio
2025-04-23 20:09   ` Darrick J. Wong
2025-04-24 12:01     ` Luca Di Maio
2025-04-24 21:55       ` Darrick J. Wong
2025-04-23 16:03 ` [PATCH v6 4/4] man: document " Luca Di Maio
2025-04-23 20:03 ` Darrick J. Wong [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=20250423200314.GG25675@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=dimitri.ledkov@chainguard.dev \
    --cc=hch@infradead.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=luca.dimaio1@gmail.com \
    --cc=smoser@chainguard.dev \
    /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