Linux-mtd Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Miquel Raynal <miquel.raynal@bootlin.com>,
	Richard Weinberger <richard@nod.at>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	linux-mtd@lists.infradead.org, Michael Walle <michael@walle.cc>
Subject: Re: [PATCH] mtd: otp: Put factory OTP/NVRAM into the entropy pool
Date: Sat, 3 Jun 2023 01:24:36 +0200	[thread overview]
Message-ID: <ZHp6NM-6Gtd68qlQ@zx2c4.com> (raw)
In-Reply-To: <20230602212318.3524782-1-linus.walleij@linaro.org>

On Fri, Jun 02, 2023 at 11:23:18PM +0200, Linus Walleij wrote:
> The factory OTP, if supported, contains factory-programmed
> information such as typically the serial number or production
> week for the chip.
> 
> As this is device-unique information, submit it into the
> system entropy pool.
> 
> This does not count as improvement of the entropy as such
> but in practice it makes it a bit more random to mix in these
> numbers.
> 
> Cc: Jason A. Donenfeld <Jason@zx2c4.com>
> Cc: Michael Walle <michael@walle.cc>
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>

Acked-by: Jason A. Donenfeld <Jason@zx2c4.com>

Great idea!

Just one question below. Feel free to disregard if it's silly.

> ---
> This is similar to the patch I made to add MMC/SD-card serial
> numbers to randomness, just with raw NOR flash.
> ---
>  drivers/mtd/mtdcore.c | 20 ++++++++++++++++++++
>  1 file changed, 20 insertions(+)
> 
> diff --git a/drivers/mtd/mtdcore.c b/drivers/mtd/mtdcore.c
> index 60670b2f70b9..efc8cf76dc60 100644
> --- a/drivers/mtd/mtdcore.c
> +++ b/drivers/mtd/mtdcore.c
> @@ -23,6 +23,7 @@
>  #include <linux/idr.h>
>  #include <linux/backing-dev.h>
>  #include <linux/gfp.h>
> +#include <linux/random.h>
>  #include <linux/slab.h>
>  #include <linux/reboot.h>
>  #include <linux/leds.h>
> @@ -966,6 +967,25 @@ static int mtd_otp_nvmem_add(struct mtd_info *mtd)
>  		}
>  
>  		if (size > 0) {
> +			/*
> +			 * The factory OTP contains thing such as a unique serial
> +			 * number and is small, so let's read it out and put it
> +			 * into the entropy pool.
> +			 */
> +			void *otp;
> +
> +			otp = kmalloc(size, GFP_KERNEL);
> +			if (!otp)
> +				return -ENOMEM;
> +			err = mtd_nvmem_fact_otp_reg_read(mtd, 0, otp, size);
> +			if (err < 0) {
> +				kfree(otp);
> +				return err;
> +			}
> +			if (err == size)
> +				add_device_randomness(otp, size);

What if instead you just did `add_device_randomness(otp, err)`, without
the conditional checking that `err == size`? You check for the actual
error case above (`err < 0`), and so in the case that
mtd_nvmem_fact_otp_reg_read() returns less than you thought it should,
it can't hurt to still add it to the rng.

Jason

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

  reply	other threads:[~2023-06-02 23:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-02 21:23 [PATCH] mtd: otp: Put factory OTP/NVRAM into the entropy pool Linus Walleij
2023-06-02 23:24 ` Jason A. Donenfeld [this message]
2023-06-03  0:14 ` Michael Walle

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=ZHp6NM-6Gtd68qlQ@zx2c4.com \
    --to=jason@zx2c4.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=michael@walle.cc \
    --cc=miquel.raynal@bootlin.com \
    --cc=richard@nod.at \
    --cc=vigneshr@ti.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