summaryrefslogtreecommitdiffstats
path: root/arch/sh
diff options
context:
space:
mode:
authorEugeniy Paltsev <Eugeniy.Paltsev@synopsys.com>2019-02-25 20:16:01 +0300
committerVineet Gupta <vgupta@synopsys.com>2019-02-25 12:11:01 -0800
commitedb64bca50cd736c6894cc6081d5263c007ce005 (patch)
tree24677adc79af060445efbc7cfe2f598fee7d1536 /arch/sh
parentfbe025c3eaf5f52060c2820eddb7357363db0d27 (diff)
downloadlinux-edb64bca50cd736c6894cc6081d5263c007ce005.tar.gz
linux-edb64bca50cd736c6894cc6081d5263c007ce005.tar.bz2
linux-edb64bca50cd736c6894cc6081d5263c007ce005.zip
ARC: u-boot args: check that magic number is correct
In case of devboards we really often disable bootloader and load Linux image in memory via JTAG. Even if kernel tries to verify uboot_tag and uboot_arg there is sill a chance that we treat some garbage in registers as valid u-boot arguments in JTAG case. E.g. it is enough to have '1' in r0 to treat any value in r2 as a boot command line. So check that magic number passed from u-boot is correct and drop u-boot arguments otherwise. That helps to reduce the possibility of using garbage as u-boot arguments in JTAG case. We can safely check U-boot magic value (0x0) in linux passed via r1 register as U-boot pass it from the beginning. So there is no backward-compatibility issues. Signed-off-by: Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com> Signed-off-by: Vineet Gupta <vgupta@synopsys.com>
Diffstat (limited to 'arch/sh')
0 files changed, 0 insertions, 0 deletions