| 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: <20160106141258.5c1e5fc6@bbrezillon>
Date: Wed, 6 Jan 2016 14:12:58 +0100
From: Boris Brezillon <boris.brezillon@...e-electrons.com>
To: Peter Pan <peterpansjtu@...il.com>
Cc: computersforpeace@...il.com, dwmw2@...radead.org,
fransklaver@...il.com, Peter Pan <peterpandong@...ron.com>,
beanhuo@...ron.com, linux-mtd@...ts.infradead.org,
linux-kernel@...r.kernel.org, karlzhang@...ron.com
Subject: Re: [PATCH v2 02/12] mtd: nand_bbt: introduce struct nand_bbt
Brian, Peter,
On Tue, 15 Dec 2015 05:59:28 +0000
Peter Pan <peterpansjtu@...il.com> wrote:
> From: Brian Norris <computersforpeace@...il.com>
>
> Currently nand_bbt.c is tied with struct nand_chip, and it makes other
> NAND family chips hard to use nand_bbt.c. Maybe it's the reason why
> onenand has own bbt(onenand_bbt.c).
>
> Separate struct nand_chip from BBT code can make current BBT shareable.
> We create struct nand_bbt to take place of nand_chip in nand_bbt.c
>
> Below is mtd folder structure we want:
> mtd
> ├── Kconfig
> ├── Makefile
> ├── ...
> ├── nand_bbt.c
> ├── nand
> │ ├── Kconfig
> │ ├── Makefile
> │ ├── nand_base.c
> │ ├── nand_ids.c
> │ ├── ...
> │ └── xway_nand.c
> ├── spi-nand
> │ ├── Kconfig
> │ ├── Makefile
> │ ├── spi-nand-base.c
> │ ├── ...
> │ └── spi-nand-device.c
> └── ...
>
> We put every information nand_bbt.c needed from outside into struct
> nand_bbt, include:
> @mtd: pointer to MTD device structure
> @is_bad_bbm: check if a block is factory bad block
> @mark_bad_bbm: imitate a block as factory bad block
> @erase: erase block bypassing resvered checks
> @bbt_options: bad block specific options. All options used
> here must come from nand_bbt.h.
> @numchips: number of physical chips, required for NAND_BBT_PERCHIP
> @bbt_td: bad block table descriptor for flash lookup.
> @bbt_md: bad block table mirror descriptor
> @chipsize: the size of one chip for multichip arrays
> @chip_shift: number of address bits in one chip
> @bbt_erase_shift: number of address bits in a bbt entry
> @page_shift: number of address bits in a page
> @bbt: bad block table pointer
>
> Signed-off-by: Brian Norris <computersforpeace@...il.com>
> [Peter: correct comment style]
> Signed-off-by: Peter Pan <peterpandong@...ron.com>
> ---
> include/linux/mtd/nand_bbt.h | 59 ++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 59 insertions(+)
>
> diff --git a/include/linux/mtd/nand_bbt.h b/include/linux/mtd/nand_bbt.h
> index 5a65230..e468571 100644
> --- a/include/linux/mtd/nand_bbt.h
> +++ b/include/linux/mtd/nand_bbt.h
> @@ -18,6 +18,8 @@
> #ifndef __LINUX_MTD_NAND_BBT_H
> #define __LINUX_MTD_NAND_BBT_H
>
> +struct mtd_info;
> +
> /* The maximum number of NAND chips in an array */
> #define NAND_MAX_CHIPS 8
>
> @@ -115,4 +117,61 @@ struct nand_bbt_descr {
> /* The maximum number of blocks to scan for a bbt */
> #define NAND_BBT_SCAN_MAXBLOCKS 4
>
> +/**
> + * struct nand_bbt - bad block table structure
> + * @mtd: pointer to MTD device structure
> + * @is_bad_bbm: check if a block is factory bad block
> + * @mark_bad_bbm: imitate a block as factory bad block
> + * @erase: erase block bypassing resvered checks
> + * @bbt_options: bad block specific options. All options used
> + * here must come from nand_bbt.h.
> + * @numchips: number of physical chips, required for NAND_BBT_PERCHIP
> + * @bbt_td: bad block table descriptor for flash lookup.
> + * @bbt_md: bad block table mirror descriptor
> + * @chipsize: the size of one chip for multichip arrays
> + * @chip_shift: number of address bits in one chip
> + * @bbt_erase_shift: number of address bits in a bbt entry
> + * @page_shift: number of address bits in a page
> + * @bbt: bad block table pointer
> + *
> + */
> +struct nand_bbt {
> + struct mtd_info *mtd;
> +
> + /*
> + * This is important to abstract out of nand_bbt.c and provide
> + * separately in nand_base.c and spi-nand-base.c -- it's sort of
> + * duplicated in nand_block_bad() (nand_base) and
> + * scan_block_fast() (nand_bbt) right now
> + *
> + * Note that this also means nand_chip.badblock_pattern should
> + * be removed from nand_bbt.c
> + */
> + int (*is_bad_bbm)(struct mtd_info *mtd, loff_t ofs);
> +
> + /*
> + * Only required if the driver wants to attempt to program new
> + * bad block markers that imitate the factory-marked BBMs
> + */
> + int (*mark_bad_bbm)(struct mtd_info *mtd, loff_t ofs);
Not sure what this function is really meant for, and it's not used in
the current patch series. Do you have an example where it would be
useful and how it would be implemented?
In any case, shouldn't we delay the creation of this method until we
have a real user?
> +
> + /* Erase a block, bypassing reserved checks */
> + int (*erase)(struct mtd_info *mtd, loff_t ofs);
Just a question about the above methods (->is_bad_bbm(),
->mark_bad_bbm() and ->erase()). Are those really meant to be defined
on a per-chip basis, or is this something set by the NAND controller, or
NAND interface common code (raw, SPI, onenand)?
In the latter case, I'd suggest defining a nand_bbt_ops struct where
you would put those methods, and then adding a
const struct nand_bbt_ops * field in nand_bbt.
I also think we should pass struct nand_bbt and not struct mtd as the
first argument of all this functions. mtd can thus be retrieved using
bbt->mtd (or even better, you could hide it behind an helper function).
> +
> + unsigned int bbt_options;
> + int numchips;
> +
> + /*
> + * Discourage new custom usages here; suggest usage of the
> + * relevant NAND_BBT_* options instead
> + */
> + struct nand_bbt_descr *bbt_td;
> + struct nand_bbt_descr *bbt_md;
> + u64 chipsize;
> + int chip_shift;
> + int bbt_erase_shift;
> + int page_shift;
> + u8 *bbt;
> +};
It seems that this nand_bbt struct is redefining some fields already
specified in nand_chip (->numchips, ->chipsize, ->chip_shift, ...), and
I guess those fields are also defined in onenand_chip and will be
defined in spi_nand_chip, so maybe it's time to create a nand_chip_info
or nand_chip_layout_info struct containing all those fields and pass a
const pointer to this struct when creating the bbt object.
Best Regards,
Boris
--
Boris Brezillon, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
--
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