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
| ||
|
Date: Tue, 5 Jan 2016 07:11:48 +0100 From: Heiko Schocher <hs@...x.de> To: Brian Norris <computersforpeace@...il.com> Cc: linux-mtd@...ts.infradead.org, Boris Brezillon <boris.brezillon@...e-electrons.com>, linux-kernel@...r.kernel.org, Frans Klaver <fransklaver@...il.com> Subject: Re: [PATCH for-4.4] mtd: nand: assign reasonable default name for NAND drivers Hello Brian, Am 04.01.2016 um 20:11 schrieb Brian Norris: > Commits such as commit 853f1c58c4b2 ("mtd: nand: omap2: show parent > device structure in sysfs") attempt to rely on the core MTD code to set > the MTD name based on the parent device. However, nand_base tries to set > a different default name according to the flash name (e.g., extracted > from the ONFI parameter page), which means NAND drivers will never make > use of the MTD defaults. This is not the intention of commit > 853f1c58c4b2. > > This results in problems when trying to use the cmdline partition > parser, since the MTD name is different than expected. Let's fix this by > providing a default NAND name, where possible. > > Note that this is not really a great default name in the long run, since > this means that if there are multiple MTDs attached to the same > controller device, they will have the same name. But that is an existing > issue and requires future work on a better controller vs. flash chip > abstraction to fix properly. > > Reported-by: Heiko Schocher <hs@...x.de> > Signed-off-by: Brian Norris <computersforpeace@...il.com> > Cc: Heiko Schocher <hs@...x.de> > Cc: Frans Klaver <fransklaver@...il.com> > --- > This patch is needed in additon to commit 472b444eef93 ("mtd: fix cmdlinepart > parser, early naming for auto-filled MTD") to fix Heiko's reported problem. At > this point, I'm not sure if this should be targeted toward late 4.4 or for 4.5. > It's a 4.4 regresssion, but a very small one. And I'm not sure if this will > have wide enough impact that it should be given a longer time to be reviewed > and tested. We can always send it to -stable later, if it's really needed. Ok... but I wonder if nobody have the same problems as I ... > drivers/mtd/nand/nand_base.c | 3 +++ > 1 file changed, 3 insertions(+) Thanks! works for me, so: Tested-by: Heiko Schocher <hs@...x.de> bye, Heiko > > diff --git a/drivers/mtd/nand/nand_base.c b/drivers/mtd/nand/nand_base.c > index ece544efccc3..9f169566fba4 100644 > --- a/drivers/mtd/nand/nand_base.c > +++ b/drivers/mtd/nand/nand_base.c > @@ -3826,6 +3826,9 @@ static struct nand_flash_dev *nand_get_flash_type(struct mtd_info *mtd, > if (!type) > type = nand_flash_ids; > > + if (!mtd->name && mtd->dev.parent) > + mtd->name = dev_name(mtd->dev.parent); > + > for (; type->name != NULL; type++) { > if (is_full_id_nand(type)) { > if (find_full_id_nand(mtd, chip, type, id_data, &busw)) > -- DENX Software Engineering GmbH, Managing Director: Wolfgang Denk HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany -- 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