linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Ben Hutchings <ben.hutchings@mind.be>
To: linux-mtd@lists.infradead.org
Cc: Ben Hutchings <ben.hutchings@mind.be>
Subject: [PATCH 0/2] mtd: ubi: Fix some initialisation failure cases
Date: Thu, 11 Apr 2024 00:42:40 +0200	[thread overview]
Message-ID: <cover.1712788087.git.ben.hutchings@mind.be> (raw)

ubi currently fails to initialise if debugfs is enabled at build time
but disabled at boot time (CONFIG_DEBUG_FS is enabled and debugfs=off
is set on the kernel command line).  Errors from debugfs should always
be ignored but this wasn't done everywhere.

While fixing this I also noticed that a recent change to ubi removed
some cleanup from the ubi_init() failure path that I think is still
needed.

This series should fix both problems.

Ben.

Ben Hutchings (2):
  mtd: ubi: Restore missing cleanup on ubi_init() failure path
  mtd: ubi: Ignore all debugfs initialisation failures

 drivers/mtd/ubi/build.c | 15 ++++++---------
 drivers/mtd/ubi/debug.c | 33 +++++++--------------------------
 drivers/mtd/ubi/debug.h |  4 ++--
 3 files changed, 15 insertions(+), 37 deletions(-)

-- 
2.39.2


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

             reply	other threads:[~2024-04-10 22:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-10 22:42 Ben Hutchings [this message]
2024-04-10 22:42 ` [PATCH 1/2] mtd: ubi: Restore missing cleanup on ubi_init() failure path Ben Hutchings
2024-04-10 22:42 ` [PATCH 2/2] mtd: ubi: Ignore all debugfs initialisation failures Ben Hutchings
2024-04-11  1:35   ` Zhihao Cheng
2024-04-11  3:30 ` [PATCH 0/2] mtd: ubi: Fix some initialisation failure cases Zhihao Cheng
2024-04-11 15:09   ` Ben Hutchings

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=cover.1712788087.git.ben.hutchings@mind.be \
    --to=ben.hutchings@mind.be \
    --cc=linux-mtd@lists.infradead.org \
    /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;
as well as URLs for NNTP newsgroup(s).