Re: UBIFS panic during brown-out

Kristof Havasi
2021-10-25T09:36:01Z

Dear Richard,

On Thu, 21 Oct 2021 at 19:44, Richard Weinberger <richard@nod.at> wrote:
>
> Kristof,
>
> ----- Ursprüngliche Mail -----
> > Von: "Kristof Havasi" <havasiefr@gmail.com>
> > An: "richard" <richard@nod.at>
> > CC: "linux-mtd" <linux-mtd@lists.infradead.org>
> > Gesendet: Donnerstag, 21. Oktober 2021 17:33:15
> > Betreff: Re: UBIFS panic during brown-out
>
> > Dear Richard,
> >
> > I noticed that I forgot to Cc linux-mtd from the previous emails.
> >
> > Latest update: we could reproduce the bug with a v5.10 port.
> > The same EPERM error is hit.
> >
> > Happy to hear any hints on how I can support in fixing this issue.
>
> so I fear you found a bug in the UBIFS auth code.
> Is it possible to share the filesystem and they keymaterial with me?

I used our build server to generate the test images, where we use one-time
throw-away keys/certs for each build. Anyway, I managed to retrieve
the key materials
for the failing v5.10-based test.

We have the following layout on the flash:
0000 - [XXX] partition for bootstrap (at91)
[XXX]- partition for UBI image

where the UBI image has:
- vol-0 DTB0 [ro]
- vol-1 DTB1 [ro]
- vol-2 Kernel0 [ro]
- vol-3 Kernel1 [ro]
- vol-4 RootFS [dyn, autoresize]

I don't know how to extract only the rootFS from the "bricked" device.
But I could dump the flash of that device and create a link for you
with that and the keys/certs.
Would that help?

>
> Thanks,
> //richard

Best Regards,
Kristóf