[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <252d1ba7-0ae0-4616-9ee7-f7c204531eaa@infradead.org>
Date: Sun, 17 Mar 2024 16:47:44 -0700
From: Randy Dunlap <rdunlap@...radead.org>
To: John Sperbeck <jsperbeck@...gle.com>,
Andrew Morton <akpm@...ux-foundation.org>, Jens Axboe <axboe@...nel.dk>,
"Peter Zijlstra (Intel)" <peterz@...radead.org>,
Thomas Gleixner <tglx@...utronix.de>,
"ndesaulniers@...gle.com" <ndesaulniers@...gle.com>
Cc: linux-kernel@...r.kernel.org, Nazerke Turtayeva <nturtayeva@...b.edu>
Subject: Re: [PATCH] init: open /initrd.image with O_LARGEFILE
Hi,
On 3/17/24 15:15, John Sperbeck wrote:
> If initrd data is larger than 2Gb, we'll eventually fail to write to
> the /initrd.image file when we hit that limit, unless O_LARGEFILE is set.
>
Could this be related to
https://lore.kernel.org/lkml/CAHY78BqCpMQptPN0SMaXuRqHOhYi+wnMEUSTYt7OHDZih4e7yQ@mail.gmail.com/
?
Thanks.
> Signed-off-by: John Sperbeck <jsperbeck@...gle.com>
> ---
> init/initramfs.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/init/initramfs.c b/init/initramfs.c
> index 76deb48c38cb..b607d3463b47 100644
> --- a/init/initramfs.c
> +++ b/init/initramfs.c
> @@ -683,7 +683,7 @@ static void __init populate_initrd_image(char *err)
>
> printk(KERN_INFO "rootfs image is not initramfs (%s); looks like an initrd\n",
> err);
> - file = filp_open("/initrd.image", O_WRONLY | O_CREAT, 0700);
> + file = filp_open("/initrd.image", O_WRONLY|O_CREAT|O_LARGEFILE, 0700);
> if (IS_ERR(file))
> return;
>
--
#Randy
Powered by blists - more mailing lists