diff options
| author | Shmulik Ladkani <shmulik.ladkani@gmail.com> | 2012-09-05 08:30:20 +0300 |
|---|---|---|
| committer | David Woodhouse <David.Woodhouse@intel.com> | 2012-09-29 15:44:25 +0100 |
| commit | 7baf04261062826ea225ab23e07c541e279143fa (patch) | |
| tree | 8cb93944ca5a5d073d7eb6868e7f67374e614fa7 /net/core/utils.c | |
| parent | 2fe87aef33b77d66fada83f5dc57b6798ad5df07 (diff) | |
mtd: cmdlinepart: make the partitions rule more strict
Huang Shijie <shijie8@gmail.com> explains:
Assume we have a 1GiB(8Gib) NAND chip, and we set the partitions
in the command line like this:
#gpmi-nand:100m(boot),100m(kernel),1g(rootfs)
In this case, the partition truncating occurs. The current code will
get the following result:
----------------------------------
root@freescale ~$ cat /proc/mtd
dev: size erasesize name
mtd0: 06400000 00040000 "boot"
mtd1: 06400000 00040000 "kernel"
----------------------------------
It is obvious that we lost the truncated partition `rootfs` which should
be 824MiB in this case.
Also, forbid 0-sized partitions.
Signed-off-by: Shmulik Ladkani <shmulik.ladkani@gmail.com>
Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>
Diffstat (limited to 'net/core/utils.c')
0 files changed, 0 insertions, 0 deletions