linux-kernel - Re: MTD: Lots of mtdblock warnings on bootup logs

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <87sf9tx7uo.fsf@miraculix.mork.no>
Date:   Wed, 12 Jul 2023 21:11:59 +0200
From:   Bjørn Mork <bjorn@...k.no>
To:     Pintu Agarwal <pintu.ping@...il.com>
Cc:     open list <linux-kernel@...r.kernel.org>,
        linux-fsdevel <linux-fsdevel@...r.kernel.org>,
        linux-mtd <linux-mtd@...ts.infradead.org>,
        linux-fsdevel@...ck.org, ezequiel@...labora.com,
        Miquel Raynal <miquel.raynal@...tlin.com>
Subject: Re: MTD: Lots of mtdblock warnings on bootup logs

Pintu Agarwal <pintu.ping@...il.com> writes:

> You mean, if someone is using "mount .. /dev/mtdblock*" then only we
> get these warnings ?
> Or, if someone is trying to access the node using open("/dev/mtdblock*") .

open() will cause a warning.

> But in this case, there should be only 1,2,3 entries but here I am
> seeing for all the NAND partitions.
> Or, is it possible that systemd-udevd is trying to access these nodes ?

Maybe?  Something trying to figure out the contents of all block devices
perhaps? 

> Can we use ubiblock for mount ubifs (rw) volumes, or here we have to
> use mtdblock ?
> We have a mixture of squashfs (ro) and ubifs (rw) ubi volumes.
> Currently, we are using the ubiblock way of mounting for squashfs but
> mtdblock mounting for ubifs.

I don't think it's safe to use mtdblock on NAND.  WHich is what the
warning is about.


Bjørn