[lkml]   [2018]   [Apr]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH v7 2/5] of: change overlay apply input data from unflattened to FDT
On 04/05/18 12:26, Rob Herring wrote:
> On Thu, Apr 5, 2018 at 2:16 PM, Frank Rowand <> wrote:
>> On 04/05/18 00:22, Jan Kiszka wrote:
>>> On 2018-04-05 02:55, Rob Herring wrote:
>>>> On Wed, Apr 4, 2018 at 5:35 PM, Jan Kiszka <> wrote:
>>>>> Hi Frank,
>>>>> On 2018-03-04 01:17, wrote:
>>>>>> From: Frank Rowand <>
>>>>>> Move duplicating and unflattening of an overlay flattened devicetree
>>>>>> (FDT) into the overlay application code. To accomplish this,
>>>>>> of_overlay_apply() is replaced by of_overlay_fdt_apply().
>>>>>> The copy of the FDT (aka "duplicate FDT") now belongs to devicetree
>>>>>> code, which is thus responsible for freeing the duplicate FDT. The
>>>>>> caller of of_overlay_fdt_apply() remains responsible for freeing the
>>>>>> original FDT.
>>>>>> The unflattened devicetree now belongs to devicetree code, which is
>>>>>> thus responsible for freeing the unflattened devicetree.
>>>>>> These ownership changes prevent early freeing of the duplicated FDT
>>>>>> or the unflattened devicetree, which could result in use after free
>>>>>> errors.
>>>>>> of_overlay_fdt_apply() is a private function for the anticipated
>>>>>> overlay loader.
>>>>> We are using of_fdt_unflatten_tree + of_overlay_apply in the
>>>>> (out-of-tree) Jailhouse loader driver in order to register a virtual
>>>>> device during hypervisor activation with Linux. The DT overlay is
>>>>> created from a a template but modified prior to application to account
>>>>> for runtime-specific parameters. See [1] for the current implementation.
>>>>> I'm now wondering how to model that scenario best with the new API.
>>>>> Given that the loader lost ownership of the unflattened tree but the
>>>>> modification API exist only for the that DT state, I'm not yet seeing a
>>>>> clear solution. Should we apply the template in disabled form (status =
>>>>> "disabled"), modify it, and then activate it while it is already applied?
>>>> No. I don't think that will work.
>>>> The of_overlay_apply() function is still there, but static. We can
>>>> export it again if the need arises.
>>> That would be the simplest solution from our perspective, but I'm not
>>> sure if that is in the original spirit of this change.
>> For short term out of tree usage, exporting of_overlay_apply() is ok.
> Meaning the out of tree users can go export it themselves.
>> Yes, for in-tree, exporting it again defeats the attempted process to
>> solve the overlay issues to make them acceptable in main line.
> The purpose of providing a function to apply an overlay in one step is
> to handle the common case and avoid open coding the sequence
> everywhere. That doesn't mean everyone will fall into the common case.

That was one of the intents behind the change.

The other intent is that with lifetime of the overlay FDT and overlay
expanded tree visible outside the devicetree core, we can not free the
overlay FDT or the overlay expanded tree because we need to protect
against use after free errors. The open coded examples of applying
overlays commonly have issues with freeing the overlay FDT and/or the
overlay expanded tree, which leads to the potential for use after free

> Of course, it also doesn't mean we have to revert back to the previous
> way to handle users that need to tweak the unflattened tree before
> applying.
> Rob

 \ /
  Last update: 2018-04-05 21:37    [W:0.058 / U:2.032 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site