All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard.weinberger@gmail.com>
To: Kristof Havasi <havasiefr@gmail.com>
Cc: Sascha Hauer <s.hauer@pengutronix.de>, linux-mtd@lists.infradead.org
Subject: Re: UBIFS-AUTH panic after reboot
Date: Thu, 17 Sep 2020 15:23:48 +0200	[thread overview]
Message-ID: <CAFLxGvw9TMHz5Mf=RYytB3N6uMuK5md+WxF=atzvaXcuibmNsg@mail.gmail.com> (raw)
In-Reply-To: <CADBnMviQd-9TbkJFUCWE8THCYF9oq-iZfu6Cjxcy9GvTfe=KUg@mail.gmail.com>

On Tue, Sep 15, 2020 at 4:51 PM Kristof Havasi <havasiefr@gmail.com> wrote:
> What I have tried:
> =================
> Based on the panic log [1], I can see that the panic happens here:
>     ubifs_lpt_calc_hash
>         `->ubifs_get_pnode
> inside the iteration over the LPT pnodes with hashing

Hmm.

> Questions:
> =========
> Q1: Are the chk_* knobs authentication aware? Or do they report so loudly
>     because I enabled the authentication and they cannot handle it yet?

They should. If not they need fixing. :-)

> Q2: Could I use `integr_chk` with authentication and so that the UBI volume is
>     my root filesystem?

What is "integr_chk"? Do you mean the integ test from mtd-utils?

> Q3: Could anyone help which tools I could use to narrow down the on the trigger?
>     E.g. Maybe with some formats combined with dynamic debugging [3]?

Let's try first with logs.

> Q4: If I stumbled upon a mainline bug, what could I do to help analysis and fix?

We will ask for what we need. No worries.
In most cases logs are fine. Sometimes a dump of a filesystem is helpful too.
Depends on the bug.

> Q5: Is there any UBIFS-Auth specific instrumentation for mkfs.ubifs apart from
>     passing in the secrets and hash-algo? IDK something like, the journal size
>     needs to be increased or other smaller detail?

Not really. It should as-is work. Otherwise mkfs.ubkfs needs fixing.

> UBIFS (ubi0:4): Mounting in authenticated mode
> UBIFS (ubi0:4): background thread "ubifs_bgt0_4" started, PID 632
> UBIFS error (ubi0:4 pid 1): ubifs_get_pnode.part.6: error -22 reading

So, it returns -EINVAL. Is this with chk_* enabled?

> pnode at 7:37186
> (pid 1) dumping pnode:
>         address c7138c80 parent c7138e80 cnext 0
>         flags 0 iip 3 level 0 num 0
>         0: free 0 dirty 255408 flags 1 lnum 0
>         1: free 0 dirty 190192 flags 1 lnum 0
>         2: free 0 dirty 255360 flags 1 lnum 0
>         3: free 0 dirty 248896 flags 1 lnum 0

Sascha, does this ring a bell?

-- 
Thanks,
//richard

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

  reply	other threads:[~2020-09-17 13:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-15 14:43 UBIFS-AUTH panic after reboot Kristof Havasi
2020-09-17 13:23 ` Richard Weinberger [this message]
2020-09-17 14:48   ` Kristof Havasi
2020-09-19 20:02     ` Richard Weinberger
2020-09-19 20:54       ` Richard Weinberger
2020-09-21  9:23         ` Kristof Havasi
2020-09-21  9:51           ` Richard Weinberger
2020-09-21 10:41             ` Kristof Havasi
2020-09-27 19:27               ` Richard Weinberger
2020-09-28  8:56                 ` Kristof Havasi
     [not found]                   ` <CADBnMvhxXdvjrA80z65zjzGffpT59+KcVq7bhqyQ7oBUpc=5=w@mail.gmail.com>
2020-09-29  8:45                     ` Richard Weinberger

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='CAFLxGvw9TMHz5Mf=RYytB3N6uMuK5md+WxF=atzvaXcuibmNsg@mail.gmail.com' \
    --to=richard.weinberger@gmail.com \
    --cc=havasiefr@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=s.hauer@pengutronix.de \
    /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.