summaryrefslogtreecommitdiffstats
path: root/arch/arm/mach-omap2/omap-smp.c
diff options
context:
space:
mode:
authorArtem Bityutskiy <Artem.Bityutskiy@nokia.com>2011-01-16 17:50:54 +0200
committerDavid Woodhouse <David.Woodhouse@intel.com>2011-01-17 15:25:48 +0000
commit154bf89f5e3e3dc59666926f27ca4a0866f39157 (patch)
treea32ef2abaa71157b2df3699b62eea774b593acb1 /arch/arm/mach-omap2/omap-smp.c
parent52d039fdaa78c5a9f9bc2940ad58d7ed76b8336d (diff)
downloadblackbird-op-linux-154bf89f5e3e3dc59666926f27ca4a0866f39157.tar.gz
blackbird-op-linux-154bf89f5e3e3dc59666926f27ca4a0866f39157.zip
mtd: mtdpart: disallow reading OOB past the end of the partition
This patch fixes the mtdpart bug which allows users reading OOB past the end of the partition. This happens because 'part_read_oob()' allows reading multiple OOB areas in one go, and mtdparts does not validate the OOB length in the request. Although there is such check in 'nand_do_read_oob()' in nand_base.c, but it checks that we do not read past the flash chip, not the partition, because in nand_base.c we work with the whole chip (e.g., mtd->size in nand_base.c is the size of the whole chip). So this check cannot be done correctly in nand_base.c and should be instead done in mtdparts.c. This problem was reported by Jason Liu <r64343@freescale.com> and reproduced with nandsim: $ modprobe nandsim first_id_byte=0x20 second_id_byte=0xaa third_id_byte=0x00 \ fourth_id_byte=0x15 parts=0x400,0x400 $ modprobe nandsim mtd_oobtest.ko dev=0 $ dmesg = snip = mtd_oobtest: attempting to read past end of device mtd_oobtest: an error is expected... mtd_oobtest: error: read past end of device = snip = mtd_oobtest: finished with 2 errors Reported-by: Jason Liu <liu.h.jason@gmail.com> Signed-off-by: Artem Bityutskiy <Artem.Bityutskiy@nokia.com> Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>
Diffstat (limited to 'arch/arm/mach-omap2/omap-smp.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud