public inbox for linux-kernel@vger.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 16:28:39 +0200	[thread overview]
Message-ID: <877cr5yzjc.fsf@miraculix.mork.no> (raw)
In-Reply-To: <CAOuPNLizjBp_8ceKq=RLznXdsHD-+N55RoPh_D7_Mpkg7M-BwQ@mail.gmail.com> (Pintu Agarwal's message of "Wed, 12 Jul 2023 19:29:39 +0530")

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

> Kernel: 5.15 ; arm64 ; NAND + ubi + squashfs
> We have some RAW partitions and one UBI partition (with ubifs/squashfs volumes).
>
> We are seeing large numbers of these logs on the serial console that
> impact the boot time.
> [....]
> [    9.667240][    T9] Creating 58 MTD partitions on "1c98000.nand":
> [....]
> [   39.975707][  T519] mtdblock: MTD device 'uefi_a' is NAND, please
> consider using UBI block devices instead.
> [   39.975707][  T519] mtdblock: MTD device 'uefi_b' is NAND, please
> consider using UBI block devices instead.
> [....]
>
> This was added as part of this commit:
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/mtd/mtdblock.c?h=v5.15.120&id=f41c9418c5898c01634675150696da290fb86796
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/mtd/mtdblock.c?h=v5.15.120&id=e07403a8c6be01857ff75060b2df9a1aa8320fe5

You have 5.15.what exactly?  commit f41c9418c5898 was added in v5.15.46.
Your log looks like it is missing.

FWIW, commit f41c9418c5898 was supposed to fix exactly that problem with
commit e07403a8c6be01.

But to catch actual mounts it will still warn if the mtdblock device is
opened.  This can obviously cause false positives if you e.g have some
script reading from the mtdblock devices.  If you are running v5.15.46 or
later then there *is* something accessing those devices. You'll have to
figure out what it is and stop it to avoid the warning.


Bjørn

  parent reply	other threads:[~2023-07-12 14:40 UTC|newest]

Thread overview: 5+ 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 14:22 ` Miquel Raynal
2023-07-12 14:28 ` Bjørn Mork [this message]
2023-07-12 18:25   ` Pintu Agarwal
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=877cr5yzjc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox