mtd: correct upper bounds check for mtd_*() APIs
authorBrian Norris <computersforpeace@gmail.com>
Tue, 22 Jul 2014 02:06:27 +0000 (19:06 -0700)
committerBrian Norris <computersforpeace@gmail.com>
Tue, 19 Aug 2014 18:53:07 +0000 (11:53 -0700)
commit0c2b4e21444d0e274e91fc7db85caddb30988853
tree32be90002a86d1fe29f1675c1baed664bcf290ff
parent36c6a7ac74044b8025488c018279115bb3c32eb0
mtd: correct upper bounds check for mtd_*() APIs

When checking the upper boundary (i.e., whether an address is higher
than the maximum size of the MTD), we should be doing an inclusive check
(greater or equal). For instance, an address of 16MB (0x1000000) on a
16MB device is invalid.

The strengthening of this bounds check is redundant for those which
already have a address+length check and ensure that the length is
non-zero, but let's just fix them all, for completeness.

Signed-off-by: Brian Norris <computersforpeace@gmail.com>
drivers/mtd/mtdcore.c