Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jarkko Sakkinen <jarkko@kernel.org>
To: buildroot@buildroot.org
Cc: Jarkko Sakkinen <jarkko@kernel.org>,
	Erik Larsson <karl.erik.larsson@gmail.com>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	James Hilliard <james.hilliard1@gmail.com>,
	"Yann E . MORIN" <yann.morin.1998@free.fr>,
	Stefan Berger <stefanb@linux.ibm.com>
Subject: [Buildroot] [PATCH v2 0/3] Upgrade systemd to v255
Date: Thu,  6 Jun 2024 13:48:10 +0300	[thread overview]
Message-ID: <20240606104813.1514-1-jarkko@kernel.org> (raw)

The goal here is to upgrade systemd version to v255, which is the final
version version with sysvinit compatibility. I also cherry-picked couple of
bug fixes from the systemd upstream, which address errors complaining of
missing superblocks:

1. Filesystem found in kernel header but not in \
   filesystems-gperf.gperf: BCACHEFS_SUPER_MAGIC
1. Filesystem found in kernel header but not in \
   filesystems-gperf.gperf: PID_FS_MAGIC

On feature side v255 has a nice tool called 'systemd-pcrlock', which can
be used for creating and experimenting with TPM2 authorization policies,
which is very useful.

I also upgraded tpm2-tools to 5.7 because it has a useful conversion
tool called 'tpm2_encodeobject".

Change Log
==========

v1: https://lists.buildroot.org/pipermail/buildroot/2024-June/754748.html

Cc: buildroot@buildroot.org.
Cc: James Hilliard <james.hilliard1@gmail.com>
CC: Arnout Vandecappelle <arnout@mind.be>
Cc: Erik Larsson <karl.erik.larsson@gmail.com>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>

Jarkko Sakkinen (3):
  package/tpm2-tools: bump version to 5.7
  package/systemd: bump to version 255
  package/systemd: add the missing superblock identifiers

 .../0001-basic-add-pidfs-magic-31709.patch    | 50 +++++++++++++++++++
 .../0002-basic-add-bcachefs-magic.patch       | 50 +++++++++++++++++++
 package/systemd/systemd.hash                  |  2 +-
 package/systemd/systemd.mk                    |  2 +-
 package/tpm2-tools/tpm2-tools.hash            |  2 +-
 package/tpm2-tools/tpm2-tools.mk              |  2 +-
 6 files changed, 104 insertions(+), 4 deletions(-)
 create mode 100644 package/systemd/0001-basic-add-pidfs-magic-31709.patch
 create mode 100644 package/systemd/0002-basic-add-bcachefs-magic.patch

--
2.45.1

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

             reply	other threads:[~2024-06-06 10:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-06 10:48 Jarkko Sakkinen [this message]
2024-06-06 10:48 ` [Buildroot] [PATCH v2 1/3] package/tpm2-tools: bump version to 5.7 Jarkko Sakkinen
2024-06-06 11:52   ` Yann E. MORIN
2024-06-06 10:48 ` [Buildroot] [PATCH v2 2/3] package/systemd: bump to version 255 Jarkko Sakkinen
2024-06-06 11:09   ` Yann E. MORIN
2024-06-06 12:17     ` Jarkko Sakkinen
2024-06-06 10:48 ` [Buildroot] [PATCH v2 3/3] package/systemd: add the missing superblock identifiers Jarkko Sakkinen
2024-06-06 11:03   ` Yann E. MORIN
2024-06-06 12:11     ` Jarkko Sakkinen
2024-06-06 11:14   ` Yann E. MORIN
2024-06-06 12:19     ` Jarkko Sakkinen

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=20240606104813.1514-1-jarkko@kernel.org \
    --to=jarkko@kernel.org \
    --cc=buildroot@buildroot.org \
    --cc=james.hilliard1@gmail.com \
    --cc=karl.erik.larsson@gmail.com \
    --cc=stefanb@linux.ibm.com \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=yann.morin.1998@free.fr \
    /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