All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bjørn Mork" <bjorn@mork.no>
To: Pintu Agarwal <pintu.ping@gmail.com>
Cc: open list <linux-kernel@vger.kernel.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	linux-mtd <linux-mtd@lists.infradead.org>,
	linux-fsdevel@kvack.org, ezequiel@collabora.com,
	Miquel Raynal <miquel.raynal@bootlin.com>
Subject: Re: MTD: Lots of mtdblock warnings on bootup logs
Date: Wed, 12 Jul 2023 21:11:59 +0200	[thread overview]
Message-ID: <87sf9tx7uo.fsf@miraculix.mork.no> (raw)
In-Reply-To: <CAOuPNLhUtVtrOQQ1Z_rA0NAerG5PSfA26=hoenuCtCBDvz1CJA@mail.gmail.com> (Pintu Agarwal's message of "Wed, 12 Jul 2023 23:55:41 +0530")

Pintu Agarwal <pintu.ping@gmail.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

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

WARNING: multiple messages have this Message-ID (diff)
From: "Bjørn Mork" <bjorn@mork.no>
To: Pintu Agarwal <pintu.ping@gmail.com>
Cc: open list <linux-kernel@vger.kernel.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	linux-mtd <linux-mtd@lists.infradead.org>,
	linux-fsdevel@kvack.org, ezequiel@collabora.com,
	Miquel Raynal <miquel.raynal@bootlin.com>
Subject: Re: MTD: Lots of mtdblock warnings on bootup logs
Date: Wed, 12 Jul 2023 21:11:59 +0200	[thread overview]
Message-ID: <87sf9tx7uo.fsf@miraculix.mork.no> (raw)
In-Reply-To: <CAOuPNLhUtVtrOQQ1Z_rA0NAerG5PSfA26=hoenuCtCBDvz1CJA@mail.gmail.com> (Pintu Agarwal's message of "Wed, 12 Jul 2023 23:55:41 +0530")

Pintu Agarwal <pintu.ping@gmail.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

  reply	other threads:[~2023-07-12 19:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-12 13:59 MTD: Lots of mtdblock warnings on bootup logs Pintu Agarwal
2023-07-12 13:59 ` Pintu Agarwal
2023-07-12 14:22 ` Miquel Raynal
2023-07-12 14:22   ` Miquel Raynal
2023-07-12 14:28 ` Bjørn Mork
2023-07-12 14:28   ` Bjørn Mork
2023-07-12 18:25   ` Pintu Agarwal
2023-07-12 18:25     ` Pintu Agarwal
2023-07-12 19:11     ` Bjørn Mork [this message]
2023-07-12 19:11       ` Bjørn Mork

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87sf9tx7uo.fsf@miraculix.mork.no \
    --to=bjorn@mork.no \
    --cc=ezequiel@collabora.com \
    --cc=linux-fsdevel@kvack.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=miquel.raynal@bootlin.com \
    --cc=pintu.ping@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.