mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Pascal Vizeli <pascal.vizeli@syshack.ch>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org, Pascal Vizeli <pvizeli@syshack.ch>
Subject: Re: [PATCH 1/1] drivers: of: bugfix partition fixups
Date: Fri, 8 Jun 2018 09:31:24 +0200	[thread overview]
Message-ID: <CACvFaDf3ivn2jQxTKdT1b1VbzhnxdEXGojd4-8pVyiSz=rcvuw@mail.gmail.com> (raw)
In-Reply-To: <20180608070540.m6etfu37vu6s64ic@pengutronix.de>

2018-06-08 9:05 GMT+02:00 Sascha Hauer <s.hauer@pengutronix.de>:
> of_find_property is not called directly from the code you are changing,
> so how excatly is the code path that fails?

of_get_reproducible_name -> of_get_property -> of_find_property

>
> What are you doing to get into this situation? This test should never
> fail or else we are in trouble. Is there some "oftree -f" command
> involved? I should really remove this command since in a device tree
> based system there are always references to device nodes which are not
> expected to become invalid.
>

Yes, I load the device tree from first bootloader and overlay some state dtbo.
But how I should do this without flush? I can do that also an a file
and load this
to bootm, but the fixups will also run on this and fails too.

I think we need remove `oftree -f` or apply this patch for hardening.

Greets
Pascal

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2018-06-08  7:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-07 17:40 Pascal Vizeli
2018-06-08  7:05 ` Sascha Hauer
2018-06-08  7:31   ` Pascal Vizeli [this message]
2018-06-11  6:41     ` Sascha Hauer

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='CACvFaDf3ivn2jQxTKdT1b1VbzhnxdEXGojd4-8pVyiSz=rcvuw@mail.gmail.com' \
    --to=pascal.vizeli@syshack.ch \
    --cc=barebox@lists.infradead.org \
    --cc=pvizeli@syshack.ch \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox