Hi Will, On 1/29/2018 9:18 PM, Will Deacon wrote: > On Wed, Jan 24, 2018 at 02:53:45PM +0530, Lingutla Chandrasekhar wrote: >> Sometime kernel image and dtb load offsets can overlap due to >> dynamically increased Image or dtb size if both load addresses >> are near to each other, which leads to bootup failures. >> >> So validate dtb load address and kernel image, if they overlap >> do not proceed to boot. >> >> Signed-off-by: Lingutla Chandrasekhar <clingutla@xxxxxxxxxxxxxx> >> --- >> >> Changes since v0: >> - Print overlap bytes. >> - Simplify ovelap checks. > This all feels a bit fragile to me, since we're relying on some portion of > the Image and .dtb working in order to run this code successfully. I'd > rather not pretend to detect this exact scenario, particularly as I can't > see it being useful for anybody other than firmware developers (who are in a > better position to check whether or not this is happening). Yes, it is useful for boot loaders, adding one more condition to current checks for bootloader failures, so that boot loader developers can easily identify the real issue(Image size increased dynamically). > More generally, is there not some .dtb checksum failure that detects > corruption there? Perhaps we could do something like that for the Image > too? In boot loader, first we load Image and then dtb to corresponding DDR offset right, so not sure checksum would help here. > Will -- To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
