From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Stefan Wahren <stefan.wahren@i2se.com>
Cc: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Stanislav Meduna <stano@meduna.org>,
linux-kernel@vger.kernel.org,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Maxime Ripard <maxime.ripard@free-electrons.com>
Subject: Re: [PATCH v2] nvmem/mxs-ocotp: fix buffer overflow in read
Date: Mon, 2 May 2016 07:44:58 -0700 [thread overview]
Message-ID: <20160502144458.GA15555@kroah.com> (raw)
In-Reply-To: <57275C69.9060902@i2se.com>
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 :(
Can you resend it in a format I can apply it in?
thanks,
greg k-h
next prev parent reply other threads:[~2016-05-02 14:45 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 [this message]
2016-05-02 14:50 ` Stefan Wahren
2016-05-02 14:58 ` Srinivas Kandagatla
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=20160502144458.GA15555@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.ripard@free-electrons.com \
--cc=srinivas.kandagatla@linaro.org \
--cc=stano@meduna.org \
--cc=stefan.wahren@i2se.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