From: Kevin Hao <haokexin@gmail.com>
To: Yocto Project <yocto@lists.yoctoproject.org>
Cc: Armin Kuster <akuster808@gmail.com>
Subject: Re: [meta-security][PATCH] dm-verity-image-initramfs: Zero out the IMAGE_ROOTFS_EXTRA_SPACE in initramfs image
Date: Tue, 5 Mar 2024 17:02:57 +0800 [thread overview]
Message-ID: <ZebfwbgtE08ONuiM@pek-khao-d3> (raw)
In-Reply-To: <20240222100738.919774-1-haokexin@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1202 bytes --]
On Thu, Feb 22, 2024 at 06:07:38PM +0800, Kevin Hao wrote:
> From: Kevin Hao <kexin.hao@windriver.com>
>
> It may trigger the following error if we set a big value to IMAGE_ROOTFS_EXTRA_SPACE.
> ERROR: dm-verity-image-initramfs-1.0-r0 do_image_cpio: The initramfs size 5308416(K) exceeds INITRAMFS_MAXSIZE: 131072(K)
>
> So zero out it for initramfs image to fix this issue. This is also what
> the initramfs images do in oe-core.
Ping.
Thanks,
Kevin
>
> Signed-off-by: Kevin Hao <kexin.hao@windriver.com>
> ---
> recipes-core/images/dm-verity-image-initramfs.bb | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/recipes-core/images/dm-verity-image-initramfs.bb b/recipes-core/images/dm-verity-image-initramfs.bb
> index 78f7b49b27d6..b6d3bdc424d2 100644
> --- a/recipes-core/images/dm-verity-image-initramfs.bb
> +++ b/recipes-core/images/dm-verity-image-initramfs.bb
> @@ -17,6 +17,7 @@ PACKAGE_INSTALL = " \
> # We want a clean, minimal image.
> IMAGE_FEATURES = ""
> IMAGE_LINGUAS = ""
> +IMAGE_ROOTFS_EXTRA_SPACE = "0"
>
> # Can we somehow inspect reverse dependencies to avoid these variables?
> python __anonymous() {
> --
> 2.40.1
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2024-03-05 9:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-22 10:07 [meta-security][PATCH] dm-verity-image-initramfs: Zero out the IMAGE_ROOTFS_EXTRA_SPACE in initramfs image Kevin Hao
2024-03-05 9:02 ` Kevin Hao [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=ZebfwbgtE08ONuiM@pek-khao-d3 \
--to=haokexin@gmail.com \
--cc=akuster808@gmail.com \
--cc=yocto@lists.yoctoproject.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 read-only IMAP folder(s) and NNTP newsgroup(s).