mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: BAREBOX <barebox@lists.infradead.org>
Subject: Re: [PATCH 0/6] partitions: GPT: refresh partition tables when necessary
Date: Wed, 7 Jan 2026 12:08:15 +0100	[thread overview]
Message-ID: <aV4-n9FvSROvNaUU@pengutronix.de> (raw)
In-Reply-To: <db44b00b-b2a5-4b06-bcbb-c579cef6622b@pengutronix.de>

On Wed, Jan 07, 2026 at 11:39:16AM +0100, Ahmad Fatoum wrote:
> Hello Sascha,
> 
> On 12/3/25 4:19 PM, Sascha Hauer wrote:
> > This is a continuation of the patch previously sent separately:
> > 
> > https://lore.kernel.org/all/20251128111929.2463263-1-s.hauer@pengutronix.de/
> > 
> > Ahmad's comment to this was that we should write the inactive GPT first
> > to make sure there's always a valid GPT on the device. This series
> > implements just that. I stumbled upon a bug when we restore the primary
> > GPT from the alternate GPT, this is fixed in this series.
> 
> I thought with this series now applied, we could wipe the first 2
> sectors and it would fall back to the alternate GPT, but this is not the
> case because partition_table_read() invokes the partition parsers only
> when partition_parser_get_by_filetype() detects the magic in the first
> two sectors.
> 
> Did you consider adapting it?

I am aware of this, but haven't looked into it.

Sascha

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |



      reply	other threads:[~2026-01-07 11:08 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-03 15:19 Sascha Hauer
2025-12-03 15:19 ` [PATCH 1/6] partitions: gpt: pass epd context pointer to find_valid_gpt() Sascha Hauer
2025-12-15 12:28   ` Ahmad Fatoum
2025-12-03 15:19 ` [PATCH 2/6] partitions: gpt: only write actual ptes size to device Sascha Hauer
2025-12-15 12:29   ` Ahmad Fatoum
2025-12-03 15:19 ` [PATCH 3/6] partitions: gpt: factor out a function to write primary/alternate GPT Sascha Hauer
2025-12-15 12:34   ` Ahmad Fatoum
2025-12-03 15:19 ` [PATCH 4/6] partitions: gpt: write inactive GPT first Sascha Hauer
2025-12-15 12:38   ` Ahmad Fatoum
2025-12-03 15:19 ` [PATCH 5/6] partitions: gpt: fix GPT restauration from alternate GPT Sascha Hauer
2025-12-15 12:41   ` Ahmad Fatoum
2025-12-03 15:19 ` [PATCH 6/6] partitions: gpt: refresh partition tables when necessary Sascha Hauer
2025-12-15 12:47   ` Ahmad Fatoum
2025-12-15 14:13     ` Sascha Hauer
2025-12-15 14:15       ` Ahmad Fatoum
2025-12-15 14:09 ` [PATCH 0/6] partitions: GPT: " Sascha Hauer
2026-01-07 10:39 ` Ahmad Fatoum
2026-01-07 11:08   ` Sascha Hauer [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=aV4-n9FvSROvNaUU@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    /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