3.16.7-ckt15 -stable review patch. If anyone has any objections, please let me
know.
--
From: JeHyeon Yeon
commit d5e7cafd69da24e6d6cc988fab6ea313a2577efc upstream.
If the part of the compression data are corrupted, or the compression
data is totally fake, the memory access
3.16.7-ckt15 -stable review patch. If anyone has any objections, please let me
know.
--
From: JeHyeon Yeon tom.y...@windriver.com
commit d5e7cafd69da24e6d6cc988fab6ea313a2577efc upstream.
If the part of the compression data are corrupted, or the compression
data is totally
From: JeHyeon Yeon
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit d5e7cafd69da24e6d6cc988fab6ea313a2577efc upstream.
If the part of the compression data are corrupted, or the compression
data is totally fake, the memory access over the
From: JeHyeon Yeon tom.y...@windriver.com
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit d5e7cafd69da24e6d6cc988fab6ea313a2577efc upstream.
If the part of the compression data are corrupted, or the compression
data is totally fake, the
3.19-stable review patch. If anyone has any objections, please let me know.
--
From: JeHyeon Yeon
commit d5e7cafd69da24e6d6cc988fab6ea313a2577efc upstream.
If the part of the compression data are corrupted, or the compression
data is totally fake, the memory access over the
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: JeHyeon Yeon
commit d5e7cafd69da24e6d6cc988fab6ea313a2577efc upstream.
If the part of the compression data are corrupted, or the compression
data is totally fake, the memory access over the
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: JeHyeon Yeon tom.y...@windriver.com
commit d5e7cafd69da24e6d6cc988fab6ea313a2577efc upstream.
If the part of the compression data are corrupted, or the compression
data is totally fake, the
3.19-stable review patch. If anyone has any objections, please let me know.
--
From: JeHyeon Yeon tom.y...@windriver.com
commit d5e7cafd69da24e6d6cc988fab6ea313a2577efc upstream.
If the part of the compression data are corrupted, or the compression
data is totally fake, the
n.
Thank you.
보낸 사람: gre...@linuxfoundation.org [gre...@linuxfoundation.org]
보낸 날짜: 2015년 3월 13일 금요일 오후 10:23
받는 사람: Yeon, JeHyeon (Tom)
참조: linux-kernel@vger.kernel.org
제목: Re: LZ4 : fix the data abort issue.
On Thu, Mar 12, 2015 at 08:28:55AM +, Yeon, JeHyeon
.
보낸 사람: gre...@linuxfoundation.org [gre...@linuxfoundation.org]
보낸 날짜: 2015년 3월 13일 금요일 오후 10:23
받는 사람: Yeon, JeHyeon (Tom)
참조: linux-kernel@vger.kernel.org
제목: Re: LZ4 : fix the data abort issue.
On Thu, Mar 12, 2015 at 08:28:55AM +, Yeon, JeHyeon (Tom
On Thu, Mar 12, 2015 at 08:28:55AM +, Yeon, JeHyeon (Tom) wrote:
> If the part of the compression data are corrupted, or the compression
> data is totally fake, the memory access over the limit is possible.
>
> This is the log from my system usning lz4 decompression.
>[6502]data abort,
On Thu, Mar 12, 2015 at 08:28:55AM +, Yeon, JeHyeon (Tom) wrote:
> If the part of the compression data are corrupted, or the compression
> data is totally fake, the memory access over the limit is possible.
>
> This is the log from my system usning lz4 decompression.
>[6502]data abort,
On Thu, Mar 12, 2015 at 08:28:55AM +, Yeon, JeHyeon (Tom) wrote:
If the part of the compression data are corrupted, or the compression
data is totally fake, the memory access over the limit is possible.
This is the log from my system usning lz4 decompression.
[6502]data abort, halting
On Thu, Mar 12, 2015 at 08:28:55AM +, Yeon, JeHyeon (Tom) wrote:
If the part of the compression data are corrupted, or the compression
data is totally fake, the memory access over the limit is possible.
This is the log from my system usning lz4 decompression.
[6502]data abort, halting
If the part of the compression data are corrupted, or the compression
data is totally fake, the memory access over the limit is possible.
This is the log from my system usning lz4 decompression.
[6502]data abort, halting
[6503]r0 0x r1 0x r2 0xdcea0ffc r3 0xdcea0ffc
If the part of the compression data are corrupted, or the compression
data is totally fake, the memory access over the limit is possible.
This is the log from my system usning lz4 decompression.
[6502]data abort, halting
[6503]r0 0x r1 0x r2 0xdcea0ffc r3 0xdcea0ffc
16 matches
Mail list logo
