All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Jens Maus via buildroot <buildroot@buildroot.org>
Cc: Jens Maus <mail@jens-maus.de>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [Buildroot] [PATCH v2] boot/grub2: fix incompat e2fsprogs feature use
Date: Thu, 12 Oct 2023 18:40:30 +0200	[thread overview]
Message-ID: <87ttqv94ld.fsf@48ers.dk> (raw)
In-Reply-To: <87il7sasu8.fsf@48ers.dk> (Peter Korsgaard's message of "Sat, 30 Sep 2023 11:55:11 +0200")

>>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:

>>>>> "Jens" == Jens Maus via buildroot <buildroot@buildroot.org> writes:
 >> With bump of package/e2fsprogs to 1.47.0 [1] a freshly generated
 >> ext4 fs has unfortunately different default features enabled
 >> (e.g. metadata_csum_seed). This and some other newer fs features
 >> (e.g. large_dir) are however not supported by our grub2.
 >> Thus, newly generated ext-based rootfs won't be recognized by grub2
 >> and are therefore not bootable/usable from grub2 anymore. This is
 >> an issue already known to other Linux derivates [2],[3],[4].

 >> This commit introduces two additional upstream patches to
 >> package/grub2 which adds EXT4_FEATURE_INCOMPAT_CSUM_SEED and
 >> EXT4_FEATURE_INCOMPAT_LARGEDIR to the EXT2_DRIVER_IGNORED_INCOMPAT
 >> list of ignored incompatible ext features, allowing grub2 to
 >> use ext filesystems with these newer default feature sets.

 >> [1] https://git.buildroot.net/buildroot/commit/?id=6a21733f839478d902f3eab287a82b456e55f708
 >> [2] https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1844012
 >> [3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031325
 >> [4] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030939

 >> Signed-off-by: Jens Maus <mail@jens-maus.de>

 >> ---
 >> Changes v1 -> v2:
 >> - added Signed-off-by and Upstream link in patches (Arnout)

 > Committed, thanks.

 > Hopefully other bootloaders will not have similar issues.

Committed to 2023.08.x, thanks.

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2023-10-12 16:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-17 20:01 [Buildroot] [PATCH 1/1] boot/grub2: fix incompat e2fsprogs feature use Jens Maus via buildroot
2023-09-22 18:04 ` Arnout Vandecappelle via buildroot
2023-09-22 18:48 ` [Buildroot] [PATCH v2] " Jens Maus via buildroot
2023-09-30  9:55   ` Peter Korsgaard
2023-10-12 16:40     ` Peter Korsgaard [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=87ttqv94ld.fsf@48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@buildroot.org \
    --cc=mail@jens-maus.de \
    --cc=thomas.petazzoni@bootlin.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 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.