From: David Disseldorp <ddiss@suse.de>
To: linux-fsdevel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
willy@infradead.org
Cc: viro@zeniv.linux.org.uk
Subject: Re: [PATCH v7 0/6] initramfs: "crc" cpio format and INITRAMFS_PRESERVE_MTIME
Date: Tue, 26 Apr 2022 11:01:19 +0200 [thread overview]
Message-ID: <20220426110119.39e823f5@suse.de> (raw)
In-Reply-To: <20220404093429.27570-1-ddiss@suse.de>
Ping...
@Matthew: "crc" archive support was added following your suggestion in
https://lore.kernel.org/all/YYwBzj0isuKOjjUe@casper.infradead.org/ -
I'd really appreciate some feedback on those patches.
On Mon, 4 Apr 2022 11:34:24 +0200, 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 4/6 to 6/6 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 v6 following feedback from Andrew Morton:
> - 3/6: improve commit message and don't split out initramfs_mtime.h
> - add extra acks and sob tags for 1/6, 2/6 and 4/6
>
> Changes since v5:
> - add PATCH 2/6 initramfs: make dir_entry.name a flexible array member
> - minor commit message rewording
>
> 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
>
> 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 | 76 ++++++++++++++++++++++++-------------
> usr/gen_init_cpio.c | 92 +++++++++++++++++++++++++++++++++------------
> 3 files changed, 127 insertions(+), 51 deletions(-)
prev parent reply other threads:[~2022-04-26 9:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-04 9:34 [PATCH v7 0/6] initramfs: "crc" cpio format and INITRAMFS_PRESERVE_MTIME David Disseldorp
2022-04-04 9:34 ` [PATCH v7 1/6] initramfs: refactor do_header() cpio magic checks David Disseldorp
2022-04-04 9:34 ` [PATCH v7 2/6] initramfs: make dir_entry.name a flexible array member David Disseldorp
2022-04-04 9:34 ` [PATCH v7 3/6] initramfs: add INITRAMFS_PRESERVE_MTIME Kconfig option David Disseldorp
2022-04-26 20:39 ` Andrew Morton
2022-04-27 21:01 ` David Disseldorp
2022-04-04 9:34 ` [PATCH v7 4/6] gen_init_cpio: fix short read file handling David Disseldorp
2022-04-26 20:40 ` Andrew Morton
2022-04-27 21:05 ` David Disseldorp
2022-04-04 9:34 ` [PATCH v7 5/6] gen_init_cpio: support file checksum archiving David Disseldorp
2022-04-04 9:34 ` [PATCH v7 6/6] initramfs: support cpio extraction with file checksums David Disseldorp
2022-04-26 9:01 ` 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=20220426110119.39e823f5@suse.de \
--to=ddiss@suse.de \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).