All of lore.kernel.org
 help / color / mirror / Atom feed
From: GangYan <gang.yan@linux.dev>
To: Matthieu Baerts <matttbe@kernel.org>
Cc: Gang Yan <yangang@kylinos.cn>, Geliang Tang <geliang@kernel.org>,
	mptcp@lists.linux.dev
Subject: Re: [PATCH] gen_initramfs.sh: use 'date -u' to get Timestamp
Date: Tue, 14 Oct 2025 09:24:39 +0800	[thread overview]
Message-ID: <aO2mV6BMsmMAcreU@yangang-ThinkPad-T14-Gen-1> (raw)
In-Reply-To: <70e9b1e4-41c4-41ba-a684-f6a0b7d7644c@kernel.org>

> On Mon, Oct 13, 2025 at 12:28:08PM +0200, Matthieu Baerts wrote:
> Hi Gang,
> 
> On 13/10/2025 12:19, Gang Yan wrote:
> > There exists a compilation error in the latest version of
> > mptcp-upstream-virtme-docker:latest:
> > '''
> > 	ERROR: Timestamp out of range for cpio format
> > 	make[4]: *** [<KERNEL_SRC>/usr/Makefile:76:
> > '''
> > 
> > The reason is the output of 'date -d0' is 'Sat Jan 1 00:00:00 UTC 0000'.
> > After using 'date -u', the output is correct.
> 
> Thank you for having looked at this. I already sent a fix in
> mptcp-upstream-virtme-docker:
> 
> 
> https://github.com/multipath-tcp/mptcp-upstream-virtme-docker/commit/52aa674
> 
This fix works well in my enviroment.

Thanks,
Gang
> The issue is in fact in Rust CoreUtils:
> 
>   https://github.com/uutils/coreutils/issues/8898
> 
> 
> Then, I don't think we need to modify the kernel source. Here are a few
> workarounds:
> 
> - Use date's GNU version: ln -sf gnudate /usr/bin/date
> 
> - Do not generate the initramfs if not needed: -d CONFIG_BLK_DEV_INITRD
> 
> - Set KBUILD_BUILD_TIMESTAMP to "-1"
> 
> WDYT?
> 
> Cheers,
> Matt
> -- 
> Sponsored by the NGI0 Core fund.
> 
> 

  parent reply	other threads:[~2025-10-14  1:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-13 10:19 [PATCH] gen_initramfs.sh: use 'date -u' to get Timestamp Gang Yan
2025-10-13 10:28 ` Matthieu Baerts
2025-10-13 13:22   ` GangYan
2025-10-14  9:44     ` Matthieu Baerts
2025-10-15  2:36       ` GangYan
2025-10-14  1:24   ` GangYan [this message]
2025-10-13 11:50 ` MPTCP CI
2025-10-13 12:23   ` Matthieu Baerts

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=aO2mV6BMsmMAcreU@yangang-ThinkPad-T14-Gen-1 \
    --to=gang.yan@linux.dev \
    --cc=geliang@kernel.org \
    --cc=matttbe@kernel.org \
    --cc=mptcp@lists.linux.dev \
    --cc=yangang@kylinos.cn \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.