From: Mimi Zohar <zohar@linux.ibm.com>
To: Christian Brauner <brauner@kernel.org>,
Roberto Sassu <roberto.sassu@huaweicloud.com>,
Danny Hu <dannyhu@arista.com>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
Roberto Sassu <roberto.sassu@huawei.com>,
Dmitry Kasatkin <dmitry.kasatkin@gmail.com>,
Eric Snowberg <eric.snowberg@oracle.com>, Jan Kara <jack@suse.cz>,
Victor Kamensky <kamensky@cisco.com>,
Taras Kondratiuk <takondra@cisco.com>,
Zheng Zengkai <zhengzengkai@huawei.com>,
zhangguangzhi <zhangguangzhi3@huawei.com>,
Jason Yan <yanaijie@huawei.com>,
silviu.vlasceanu@huawei.com, hpa@zytor.com, arnd@arndb.de,
james.w.mcmechan@gmail.com, niveditas98@gmail.com,
pierre@arista.com, julien@arista.com, kbharathi@arista.com,
alexandr.lobakin@intel.com, linux-fsdevel@vger.kernel.org,
linux-integrity@vger.kernel.org,
linux-security-module@vger.kernel.org,
linux-kbuild@vger.kernel.org, initramfs@vger.kernel.org,
linux-api@vger.kernel.org, linux-kernel@vger.kernel.org,
bug-cpio@gnu.org
Subject: Re: [PATCH v6 0/4] initramfs: add support for xattrs in the initial ram disk
Date: Fri, 20 Nov 2026 05:49:03 -0500 [thread overview]
Message-ID: <bff9077bad99a5b2c9137a44d98be8fd16be7b48.camel@linux.ibm.com> (raw)
In-Reply-To: <20261117-makaber-paranoia-gefilde-7d976e97e12a@brauner>
Hi Christian,
On Tue, 2026-11-17 at 15:04 +0100, Christian Brauner wrote:
> If you want xattrs in the initramfs then that needs to be a proper,
> versioned cpio format that userspace tooling understands. I'm not
> taking METADATA!!!. So still no, sorry.
Regarding your request for a versioned cpio format, that is the first approach
we tried. I posted an RFC extending newc with xattrs in January 2015 [1],
followed by a v1 later that month [2], after Al Viro advised extending cpio at
the 2014 Kernel Summit. Taras Kondratiuk and Victor Kamensky carried the work
forward in 2018 as "newcx" [3]. The discussion then turned to redesigning the
format itself: ASCII fixed-width fields, no header length, the in-band
TRAILER!!! end marker, and whether to use pax/tar instead [4].
Roberto’s later series [5], carried forward by Danny Hu in v6 [6], aimed to
provide xattr support within the existing format, since the format discussion
had stalled. It began with xattrs in separate files and later moved to a
metadata file placed after each file it describes, following review comments
asking for self-contained per-file records that work when several initramfs
archives are loaded.
I wanted to share this background in case it’s useful to whoever takes on a new
versioned cpio format with xattr support.
Thanks,
Mimi
References:
[1] RFC, Jan 2015, extend initramfs archive format to support xattrs:
https://lore.kernel.org/all/1584934.WkKQGAFadF@sifl/T/
[2] v1, Jan 2015:
https://lore.kernel.org/lkml/1421781180-24425-1-git-send-email-zohar@linux.vnet.ibm.com/
[3] newcx v3, Feb 2018 (Taras Kondratiuk):
https://lore.kernel.org/all/1519153284.14218.18.camel@tycho.nsa.gov/t/
[4] Why cpio rather than tar:
https://www.kernel.org/doc/Documentation/filesystems/ramfs-rootfs-initramfs.rst
[5] v3, May 2019 (Roberto Sassu):
https://lore.kernel.org/lkml/20190517165519.11507-1-roberto.sassu@huawei.com/
[6] v6, Nov 2026 (Danny Hu):
https://lore.kernel.org/linux-integrity/20261105193743.2654656-1-dannyhu@arista.com/
prev parent reply other threads:[~2026-11-20 10:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 19:37 Danny Hu
2026-11-05 19:37 ` [PATCH v6 1/4] ima: skip algorithm availability check until initramfs unpacking is finished Danny Hu
2026-11-05 19:37 ` [PATCH v6 2/4] initramfs: add file metadata Danny Hu
2026-11-05 19:37 ` [PATCH v6 3/4] initramfs: read metadata from special file METADATA!!! Danny Hu
2026-11-05 19:37 ` [PATCH v6 4/4] gen_init_cpio: add support for file metadata Danny Hu
2026-11-10 16:21 ` [PATCH v6 0/4] initramfs: add support for xattrs in the initial ram disk Christian Brauner
2026-11-11 13:45 ` Roberto Sassu
2026-11-11 18:44 ` Mimi Zohar
2026-11-17 14:04 ` Christian Brauner
2026-11-20 10:49 ` Mimi Zohar [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=bff9077bad99a5b2c9137a44d98be8fd16be7b48.camel@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=alexandr.lobakin@intel.com \
--cc=arnd@arndb.de \
--cc=brauner@kernel.org \
--cc=bug-cpio@gnu.org \
--cc=dannyhu@arista.com \
--cc=dmitry.kasatkin@gmail.com \
--cc=eric.snowberg@oracle.com \
--cc=hpa@zytor.com \
--cc=initramfs@vger.kernel.org \
--cc=jack@suse.cz \
--cc=james.w.mcmechan@gmail.com \
--cc=julien@arista.com \
--cc=kamensky@cisco.com \
--cc=kbharathi@arista.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=niveditas98@gmail.com \
--cc=pierre@arista.com \
--cc=roberto.sassu@huawei.com \
--cc=roberto.sassu@huaweicloud.com \
--cc=silviu.vlasceanu@huawei.com \
--cc=takondra@cisco.com \
--cc=viro@zeniv.linux.org.uk \
--cc=yanaijie@huawei.com \
--cc=zhangguangzhi3@huawei.com \
--cc=zhengzengkai@huawei.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
all inboxes | Powered by JetHome®