From: Liam Girdwood <lrg@ti.com>
To: Axel Lin <axel.lin@gmail.com>
Cc: Samuel Ortiz <sameo@linux.intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Graeme Gregory <gg@slimlogic.co.uk>,
Jorge Eduardo Candelaria <jedu@slimlogic.co.uk>
Subject: Re: [PATCH] mfd: Fix off-by-one value range checking for tps65910_i2c_write
Date: Mon, 16 May 2011 13:26:03 +0100 [thread overview]
Message-ID: <4DD117DB.4070204@ti.com> (raw)
In-Reply-To: <20110513174606.GV8970@sortiz-mobl>
On 13/05/11 18:46, Samuel Ortiz wrote:
> Hi Axel,
>
> On Fri, May 13, 2011 at 05:13:57PM +0800, Axel Lin wrote:
>> If bytes == (TPS65910_MAX_REGISTER + 1), we have a buffer overflow when
>> doing memcpy(&msg[1], src, bytes).
> This code is going through Liam's tree, I'm adding him to this thread.
> Liam, please add my Acked-by to this patch, if you think it's needed.
>
Axel, could you resend to me with Samuels Ack and I'll apply.
Thanks
Liam
prev parent reply other threads:[~2011-05-16 12:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-13 9:13 [PATCH] mfd: Fix off-by-one value range checking for tps65910_i2c_write Axel Lin
2011-05-13 17:46 ` Samuel Ortiz
2011-05-16 12:26 ` Liam Girdwood [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=4DD117DB.4070204@ti.com \
--to=lrg@ti.com \
--cc=axel.lin@gmail.com \
--cc=gg@slimlogic.co.uk \
--cc=jedu@slimlogic.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=sameo@linux.intel.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