From: Florian Fainelli <f.fainelli@gmail.com>
To: Willy Tarreau <w@1wt.eu>
Cc: stable@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
donb@securitymouse.com, Willem Pinckaers <willem@lekkertech.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: lzo: check for length overrun in variable length encoding backport
Date: Thu, 25 Jun 2015 20:00:20 -0700 [thread overview]
Message-ID: <558CC044.1030108@gmail.com> (raw)
In-Reply-To: <20150625053031.GB19787@1wt.eu>
Le 06/24/15 22:30, Willy Tarreau a écrit :
> Hi Florian,
>
> On Wed, Jun 24, 2015 at 09:48:46PM -0700, Florian Fainelli wrote:
>> Hi,
>>
>> Could you backport this commit:
>> 72cf90124e87d975d0b2114d930808c58b4c05e4 ("lzo: check for length overrun
>> in variable length encoding.") into stable kernels older than 3.18?
>>
>> It should apply cleanly to anything that contains
>> 8b975bd3f9089f8ee5d7bbfd798537b992bbc7e7 ("lib/lzo: Update LZO
>> compression to current upstream version") which goes as far as 3.9.
>
> Well, it was merged into 3.10.59 as commit 9689415259, 3.12.32 as 4277fc42,
> 3.14.23 as 7f5f71a92.
>
> Are you sure you didn't mean something else and confused it with another id ?
I just got confused with searching the original commit it and did not
search by subject, thanks for the confirmation and sorry for the noise.
--
Florian
prev parent reply other threads:[~2015-06-26 3:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-25 4:48 lzo: check for length overrun in variable length encoding backport Florian Fainelli
2015-06-25 5:30 ` Willy Tarreau
2015-06-26 3:00 ` Florian Fainelli [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=558CC044.1030108@gmail.com \
--to=f.fainelli@gmail.com \
--cc=donb@securitymouse.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=w@1wt.eu \
--cc=willem@lekkertech.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.