diff options
| author | Daniel Golle <daniel@makrotopia.org> | 2022-05-01 14:13:01 +0100 |
|---|---|---|
| committer | Daniel Golle <daniel@makrotopia.org> | 2022-05-01 16:56:39 +0100 |
| commit | 0917d223d14bca9edd3f8c91e2828a7a960a21d1 (patch) | |
| tree | 5f3a9a035782767713511ecb78abd47a5610fad6 /libfstools/mount.c | |
| parent | 898b328d9ee4b0158df5a972d19924864ec9bfaf (diff) | |
| download | fstools-0917d223d14bca9edd3f8c91e2828a7a960a21d1.tar.gz | |
block: don't probe mtdblock on NAND (with legacy exceptions)
Recent kernels started to spill warnings on the log if a userspace
process open()s an mtdblock device backed by NAND flash:
mtdblock: MTD device 'foo' is NAND, please consider using UBI block devices instead.
The warning itself is legitimate -- one really shouldn't be using
mtdblock on NAND.
Hence make fstools skip probing mtdblock devices if their underlaying
mtd device is of type 'nand'. As we don't want to break boards actually
using JFFS2 and squashfs directly on NAND, still probe the mtdblock
device in case the mtd device name is 'rootfs' or 'rootfs_data'.
This will then also trigger the kernel warning as it should.
Signed-off-by: Daniel Golle <daniel@makrotopia.org>
Diffstat (limited to 'libfstools/mount.c')
0 files changed, 0 insertions, 0 deletions