linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: stefan.wahren@i2se.com (Stefan Wahren)
To: linux-arm-kernel@lists.infradead.org
Subject: nvmem: mxs-ocotp read problem
Date: Tue, 26 Apr 2016 14:59:41 +0200	[thread overview]
Message-ID: <571F663D.5080703@i2se.com> (raw)
In-Reply-To: <571F54DF.9020902@meduna.org>

Hi Stano,

Am 26.04.2016 um 13:45 schrieb Stanislav Meduna:
> Hi,
>
> the mxs_ocotp_read seems to incorrectly iterate through
> the memory to be read, resulting in a buffer overflow/off-area
> access and sometimes oops. 

could you please provide me scenario, so i can test it.

Regards
Stefan

> The following patch seems to fix
> the problem
>
> Regards
>                                Stano
>
>
> diff --git a/drivers/nvmem/mxs-ocotp.c b/drivers/nvmem/mxs-ocotp.c
> index 8ba19bb..914a4fa 100644
> --- a/drivers/nvmem/mxs-ocotp.c
> +++ b/drivers/nvmem/mxs-ocotp.c
> @@ -94,7 +94,7 @@ static int mxs_ocotp_read(void *context, const void *reg, size_t reg_size,
>         if (ret)
>                 goto close_banks;
>
> -       while (val_size) {
> +       while (val_size >= reg_size) {
>                 if ((offset < OCOTP_DATA_OFFSET) || (offset % 16)) {
>                         /* fill up non-data register */
>                         *buf = 0;
> @@ -103,7 +103,7 @@ static int mxs_ocotp_read(void *context, const void *reg, size_t reg_size,
>                 }
>
>                 buf++;
> -               val_size--;
> +               val_size -= reg_size;
>                 offset += reg_size;
>         }

      reply	other threads:[~2016-04-26 12:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-26 11:45 nvmem: mxs-ocotp read problem Stanislav Meduna
2016-04-26 12:59 ` Stefan Wahren [this message]

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=571F663D.5080703@i2se.com \
    --to=stefan.wahren@i2se.com \
    --cc=linux-arm-kernel@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).