sandbox: mmc: Start off with a zeroed file

When running multiple tests the mmc emulator calls malloc() to obtain the
memory for its disk image. Since the memory is not cleared, it is possible
that it happens to contain a partition table.

The dm_test_part() test (for one) relies on mmc0 being empty on startup.
Zero the memory to ensure that it is.

Signed-off-by: Simon Glass <sjg@chromium.org>

diff --git a/drivers/mmc/sandbox_mmc.c b/drivers/mmc/sandbox_mmc.c
index ba79a5565c38ecf67dae584d7b0131549e27b2ed..0ba7940a4dbfc41308182ad2023e1c9b82f748a7 100644 (file)
--- a/drivers/mmc/sandbox_mmc.c
+++ b/drivers/mmc/sandbox_mmc.c
@@ -183,7 +183,7 @@ static int sandbox_mmc_probe(struct udevice *dev)
                priv->csize = 0;
                priv->size = (priv->csize + 1) * SIZE_MULTIPLE; /* 1 MiB */
 
-               priv->buf = malloc(priv->size);
+               priv->buf = calloc(1, priv->size);
                if (!priv->buf) {
                        log_err("%s: Not enough memory (%x bytes)\n",
                                dev->name, priv->size);