| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <CAMiH66H5rfzfPJ8trbnHxWVL4icHVBq+QYVhS79HQa_emoTJmQ@mail.gmail.com> Date: Fri, 31 Aug 2012 10:30:46 -0400 From: Huang Shijie <shijie8@...il.com> To: dedekind1@...il.com Cc: dwmw2@...radead.org, linux-mtd@...ts.infradead.org, linux-kernel@...r.kernel.org, shmulik.ladkani@...il.com Subject: Re: [PATCH 1/3] mtd: cmdlinepart: make the partitions rule more strict On Fri, Aug 31, 2012 at 7:45 AM, Artem Bityutskiy <dedekind1@...il.com> wrote: > On Sun, 2012-08-26 at 13:21 -0400, Huang Shijie wrote: >> There are typically two types to set the mtd partitions: >> >> <1> set with the `size`, such as >> gpmi-nand:100m(boot),100m(kernel),1g(rootfs) >> >> <2> set with the `offset`, such as >> gpmi-nand:100m@0(boot),100m@...m(kernel),1g@...m(rootfs) >> gpmi-nand:1g@...m(rootfs),100m@0(boot),100m@...m(kernel) >> >> If we mix these two types, such as: >> gpmi-nand:100m@0(boot),100m(kernel),1g@...m(rootfs) >> gpmi-nand:1g@...m(rootfs),100m@0(boot),100m(kernel) >> >> It's hard to understand the cmdline. And also it is hard to sort the >> partitions in this mixed type. So we explicitly forbid the mixed type. > > So "explicitly forbid" is just to add a "do not do this" comment? > Do you think we should change the code to forbid this mixed type? Huang Shijie -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists