Re: [PATCH v2] riscv: Fix memblock reservation for device tree blob

2019-10-04 Thread Paul Walmsley
On Fri, 27 Sep 2019, Albert Ou wrote: > This fixes an error with how the FDT blob is reserved in memblock. > An incorrect physical address calculation exposed the FDT header to > unintended corruption, which typically manifested with of_fdt_raw_init() > faulting during late boot after fdt_totalsiz

Re: [PATCH v2] riscv: Fix memblock reservation for device tree blob

2019-09-28 Thread Anup Patel
On Sat, Sep 28, 2019 at 11:52 AM Bin Meng wrote: > > On Sat, Sep 28, 2019 at 7:14 AM Albert Ou wrote: > > > > This fixes an error with how the FDT blob is reserved in memblock. > > An incorrect physical address calculation exposed the FDT header to > > unintended corruption, which typically manif

Re: [PATCH v2] riscv: Fix memblock reservation for device tree blob

2019-09-27 Thread Bin Meng
On Sat, Sep 28, 2019 at 7:14 AM Albert Ou wrote: > > This fixes an error with how the FDT blob is reserved in memblock. > An incorrect physical address calculation exposed the FDT header to > unintended corruption, which typically manifested with of_fdt_raw_init() > faulting during late boot after

[PATCH v2] riscv: Fix memblock reservation for device tree blob

2019-09-27 Thread Albert Ou
This fixes an error with how the FDT blob is reserved in memblock. An incorrect physical address calculation exposed the FDT header to unintended corruption, which typically manifested with of_fdt_raw_init() faulting during late boot after fdt_totalsize() returned a wrong value. Systems with smalle