All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Disseldorp <ddiss@suse.de>
To: linux-fsdevel@vger.kernel.org
Cc: Martin Wilck <mwilck@suse.com>,
	viro@zeniv.linux.org.uk, willy@infradead.org
Subject: Re: initramfs: "crc" cpio format and INITRAMFS_PRESERVE_MTIME
Date: Mon, 20 Dec 2021 17:05:36 +0100	[thread overview]
Message-ID: <20211220170536.7d0b7b28@suse.de> (raw)
In-Reply-To: <20211213232007.26851-1-ddiss@suse.de>

On Tue, 14 Dec 2021 00:20:03 +0100, David Disseldorp wrote:

> This patchset does some minor initramfs refactoring and allows cpio
> entry mtime preservation to be disabled via a new Kconfig
> INITRAMFS_PRESERVE_MTIME option.
> Patches 3/5 to 5/5 implement support for creation and extraction of
> "crc" cpio archives, which carry file data checksums. Basic tests for
> this functionality can be found at
> Link: https://github.com/rapido-linux/rapido/pull/163
> 
> Changes since v4, following feedback from Matthew Wilcox:
> - implement cpio "crc" archive creation and extraction
> - add patch to fix gen_init_cpio short read handling
> - drop now-unnecessary "crc" documentation and error msg changes

Ping, any feedback on this round?

Thanks, David

> Changes since v3, following feedback from Martin Wilck:
> - 4/4: keep vfs_utimes() call in do_copy() path
>   + drop [PATCH v3 4/5] initramfs: use do_utime() wrapper consistently
>   + add do_utime_path() helper
>   + clean up timespec64 initialisation
> - 4/4: move all mtime preservation logic to initramfs_mtime.h and drop
>   separate .c
> - 4/4: improve commit message
> 
> 
>  init/Kconfig           | 10 +++++
>  init/initramfs.c       | 89 +++++++++++++++-------------------------
>  init/initramfs_mtime.h | 50 +++++++++++++++++++++++
>  usr/gen_init_cpio.c    | 92 ++++++++++++++++++++++++++++++------------
>  4 files changed, 159 insertions(+), 82 deletions(-)

      parent reply	other threads:[~2021-12-20 16:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-13 23:20 initramfs: "crc" cpio format and INITRAMFS_PRESERVE_MTIME David Disseldorp
2021-12-13 23:20 ` [PATCH v5 1/5] initramfs: refactor do_header() cpio magic checks David Disseldorp
2021-12-13 23:20 ` [PATCH v5 2/5] initramfs: add INITRAMFS_PRESERVE_MTIME Kconfig option David Disseldorp
2022-01-05 20:10   ` David Disseldorp
2021-12-13 23:20 ` [PATCH v5 3/5] gen_init_cpio: fix short read file handling David Disseldorp
2021-12-13 23:20 ` [PATCH v5 4/5] gen_init_cpio: support file checksum archiving David Disseldorp
2021-12-13 23:20 ` [PATCH v5 5/5] initramfs: support cpio extraction with file checksums David Disseldorp
2021-12-20 16:05 ` David Disseldorp [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=20211220170536.7d0b7b28@suse.de \
    --to=ddiss@suse.de \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=mwilck@suse.com \
    --cc=viro@zeniv.linux.org.uk \
    --cc=willy@infradead.org \
    /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.