mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: "Enrico Jörns" <ejo@pengutronix.de>
To: barebox@lists.infradead.org
Cc: "Enrico Jörns" <ejo@pengutronix.de>
Subject: [PATCH] block: don't error while flushing when write support is disabled
Date: Thu, 15 Jan 2026 15:24:01 +0100	[thread overview]
Message-ID: <20260115142410.3422704-1-ejo@pengutronix.de> (raw)

If write support for the underlying device is disabled (e.g. by
disabling CONFIG_MCI_WRITE), blk->ops->write will be NULL.
Unconditionally dereferencing/calling blk->ops->write() results in a
NULL pointer dereference.

Fix this by making chunk_flush() a noop for missing write support.
Don't return an error since there should be nothing to flush if write
support is disabled, anyway.

Note that barebox currently does not prevent calling write/flush
operations, even if CONFIG_MCI_WRITE and thus write support is actually
disabled.
But this should be handled on another level.

Signed-off-by: Enrico Jörns <ejo@pengutronix.de>
---
 common/block.c | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/common/block.c b/common/block.c
index ca2ed37dbd..abd05eab39 100644
--- a/common/block.c
+++ b/common/block.c
@@ -60,6 +60,9 @@ static int chunk_flush(struct block_device *blk, struct chunk *chunk)
 	if (!chunk->dirty)
 		return 0;
 
+	if (!blk->ops->write)
+		return 0;
+
 	len = writebuffer_io_len(blk, chunk);
 	ret = blk->ops->write(blk, chunk->data, chunk->block_start, len);
 	if (ret < 0)
-- 
2.47.3




             reply	other threads:[~2026-01-15 14:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-15 14:24 Enrico Jörns [this message]
2026-01-15 14:52 ` Ahmad Fatoum
2026-01-16  7:12 ` Sascha Hauer

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=20260115142410.3422704-1-ejo@pengutronix.de \
    --to=ejo@pengutronix.de \
    --cc=barebox@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