From: Jan Kiszka <jan.kiszka@siemens.com>
To: "Bezdeka,
Florian (T RDA IOT SES-DE)" <florian.bezdeka@siemens.com>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Cc: "Schild, Henning (T RDA IOT SES-DE)" <henning.schild@siemens.com>,
"Gylstorff,
Quirin (T RDA IOT SES-DE)" <quirin.gylstorff@siemens.com>
Subject: Re: [RFC PATCH 0/2] wic: warn on usage of Y2038 affected file systems
Date: Sat, 27 Mar 2021 08:20:56 +0100 [thread overview]
Message-ID: <ef877bf6-435b-2a83-461f-501129354b01@siemens.com> (raw)
In-Reply-To: <20210201185815.382326-1-florian.bezdeka@siemens.com>
On 01.02.21 19:58, Bezdeka, Florian (T RDA IOT SES-DE) wrote:
> Valid workarounds found so far:
> - Tell wic that an partition will grow:
> Add `--mkfs-extraopts "-T ext4"` to your wic partition definition
> - Set the inode size to 256 (for small ext4 partitions)
> Add `--mkfs-extraopts "-I 256"` to your wic partition definition
Is this check is currently part of Isar (triggering on one of my layers
at least) and will eventually come back via OE, concrete help how to
resolve the warning should become part of Isar as well.
Apparently, --mkfs-extraopts "-T default" is the common pattern now, right?
Jan
--
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2021-03-27 7:25 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-01 18:58 florian.bezdeka
2021-02-01 18:58 ` [RFC PATCH 1/2] wic-img: Forward warnings from wic to bitbake florian.bezdeka
2021-02-01 18:58 ` [RFC PATCH 2/2] wic: Warn if an ext filesystem affected by the Y2038 problem is used florian.bezdeka
2021-02-11 8:07 ` [RFC PATCH 0/2] wic: warn on usage of Y2038 affected file systems Anton Mikanovich
2021-02-11 8:23 ` Henning Schild
2021-02-11 9:09 ` Jan Kiszka
2021-02-11 9:57 ` florian.bezdeka
2021-02-11 10:21 ` Henning Schild
2021-02-11 12:47 ` florian.bezdeka
2021-02-11 13:31 ` florian.bezdeka
2021-02-11 14:13 ` Henning Schild
2021-02-11 17:57 ` Jan Kiszka
2021-02-11 18:01 ` Henning Schild
2021-02-17 11:56 ` Baurzhan Ismagulov
2021-03-01 15:18 ` [PATCH] wic: Warn if an ext filesystem affected by the Y2038 problem is used Florian Bezdeka
2021-03-01 15:23 ` vijaikumar....@gmail.com
2021-03-01 15:38 ` florian.bezdeka
2021-03-01 15:58 ` vijaikumar....@gmail.com
2021-03-01 17:22 ` Jan Kiszka
2021-03-01 17:45 ` florian.bezdeka
2021-03-01 17:54 ` vijaikumar....@gmail.com
2021-03-02 9:20 ` Henning Schild
2021-03-02 10:12 ` Jan Kiszka
2021-03-27 7:20 ` Jan Kiszka [this message]
2021-03-27 8:54 ` [RFC PATCH 0/2] wic: warn on usage of Y2038 affected file systems Florian Bezdeka
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=ef877bf6-435b-2a83-461f-501129354b01@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=florian.bezdeka@siemens.com \
--cc=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=quirin.gylstorff@siemens.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