linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: srinivas.kandagatla@linaro.org (Srinivas Kandagatla)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] nvmem/mxs-ocotp: fix buffer overflow in read
Date: Mon, 2 May 2016 15:58:56 +0100	[thread overview]
Message-ID: <57276B30.8080909@linaro.org> (raw)
In-Reply-To: <5727694B.80708@i2se.com>

Hi Stefan,


On 02/05/16 15:50, Stefan Wahren wrote:
> Hi Stano,
>
> Am 02.05.2016 um 16:44 schrieb Greg Kroah-Hartman:
>> On Mon, May 02, 2016 at 03:55:53PM +0200, Stefan Wahren wrote:
>>> Hi Srinivas,
>>> hi Greg,
>>>
>>> Am 27.04.2016 um 14:39 schrieb Stanislav Meduna:
>>>> This patch fixes the issue where the mxs_ocotp_read is reading
>>>> the ocotp in reg_size steps but decrements the remaining size
>>>> by 1. The number of iterations is thus four times higher,
>>>> overwriting the area behind the output buffer.
>>>>
>>>> Fixes: c01e9a11ab6f ("nvmem: add driver for ocotp in i.MX23 and i.MX28")
>>>> Tested-by: Stefan Wahren <stefan.wahren@i2se.com>
>>>> Signed-off-by: Stanislav Meduna <stano@meduna.org>
>>> any change to get this critical fix into 4.6?
>> This is the first I've seen this patch :(
>
> sorry for this.
>
>>
>> Can you resend it in a format I can apply it in?
>
> Could you please resend V2 to Greg?

I will re-send this patch to Greg in next few mins..

thanks,
srini

>
> Thanks
> Stefan
>
>>
>> thanks,
>>
>> greg k-h
>>
>> _______________________________________________
>> linux-arm-kernel mailing list
>> linux-arm-kernel at lists.infradead.org
>> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
>

      reply	other threads:[~2016-05-02 14:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-27 12:39 [PATCH v2] nvmem/mxs-ocotp: fix buffer overflow in read Stanislav Meduna
2016-05-02 13:55 ` Stefan Wahren
2016-05-02 14:44   ` Greg Kroah-Hartman
2016-05-02 14:50     ` Stefan Wahren
2016-05-02 14:58       ` Srinivas Kandagatla [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=57276B30.8080909@linaro.org \
    --to=srinivas.kandagatla@linaro.org \
    --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).