mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christian Brauner <brauner@kernel.org>
To: Roberto Sassu <roberto.sassu@huaweicloud.com>,
	 Danny Hu <dannyhu@arista.com>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
	 Mimi Zohar <zohar@linux.ibm.com>,
	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: Tue, 17 Nov 2026 15:04:54 +0100	[thread overview]
Message-ID: <20261117-makaber-paranoia-gefilde-7d976e97e12a@brauner> (raw)
In-Reply-To: <a9edb8a433e8efcba3d11b2a06fa1063df41a24d.camel@huaweicloud.com>

On Wed, Nov 11, 2026 at 02:45:34PM +0100, Roberto Sassu wrote:
> Similarly, the archive can already ship arbitrary binaries that get
> executed as root. If you want, we could restrict it to security.ima and
> security.evm only.

That doesn't change anything about my main objection. It's still
in-band signalling via a magic filename that changes the meaning of
what came before it in the stream and that no cpio tool knows about.
We're not complicating cpio. It's point was to be so dumb that the
kernel can safely unpack it.

> I agree when the image is prebuilt and has a known reference value. As
> far as I know, there is no reference value when the initial ram disk is
> dynamically generated on the host. In the latter case, using finer-
> granularity measurement/appraisal is the only option.

Whatever generates the initrd on the host can sign or measure the image
it produces. That's not a reason to teach the kernel to apply xattrs
from magic files during early boot.

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.

And to Mimi's point that nobody maintained initramfs back then: it's
part of the VFS entry in MAINTAINERS now and we maintain it.

  parent reply	other threads:[~2026-11-17 14:05 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 [this message]
2026-11-20 10:49       ` Mimi Zohar

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=20261117-makaber-paranoia-gefilde-7d976e97e12a@brauner \
    --to=brauner@kernel.org \
    --cc=alexandr.lobakin@intel.com \
    --cc=arnd@arndb.de \
    --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 \
    --cc=zohar@linux.ibm.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®