Minchan Kim writes:
> On Wed, Aug 02, 2017 at 02:24:20PM +1000, Michael Ellerman wrote:
>> Minchan Kim writes:
>> > From 0ffbd3c8769fdf56e2f14908f890f9d1703ed32e Mon Sep 17 00:00:00 2001
>> > From: Minchan Kim
>> > Date: Tue, 25 Jul 2017 15:15:18 +0900
>> > Subject: [PATCH] zram: do not free poo
Hi Michael,
On Wed, Aug 02, 2017 at 02:24:20PM +1000, Michael Ellerman wrote:
> Minchan Kim writes:
> > From 0ffbd3c8769fdf56e2f14908f890f9d1703ed32e Mon Sep 17 00:00:00 2001
> > From: Minchan Kim
> > Date: Tue, 25 Jul 2017 15:15:18 +0900
> > Subject: [PATCH] zram: do not free pool->size_class
>
Minchan Kim writes:
> From 0ffbd3c8769fdf56e2f14908f890f9d1703ed32e Mon Sep 17 00:00:00 2001
> From: Minchan Kim
> Date: Tue, 25 Jul 2017 15:15:18 +0900
> Subject: [PATCH] zram: do not free pool->size_class
>
> Mike reported kernel goes oops with ltp:zram03 testcase.
...
>
> He bisected the probl
On Tue, 2017-07-25 at 15:26 +0900, Minchan Kim wrote:
> Hi,
>
> On Mon, Jul 24, 2017 at 08:17:01PM +0200, Mike Galbraith wrote:
> > Now bisected and verified via revert, the culprit is:
> >
> > cf8e0fedf078 mm/zsmalloc: simplify zs_max_alloc_size handling
> >
> > Reproducer: ltp::testcases/bin/z
Hi,
On Mon, Jul 24, 2017 at 08:17:01PM +0200, Mike Galbraith wrote:
> Now bisected and verified via revert, the culprit is:
>
> cf8e0fedf078 mm/zsmalloc: simplify zs_max_alloc_size handling
>
> Reproducer: ltp::testcases/bin/zram03.
>
Thanks for the report and bisecting.
I believe this patch s
Now bisected and verified via revert, the culprit is:
cf8e0fedf078 mm/zsmalloc: simplify zs_max_alloc_size handling
Reproducer: ltp::testcases/bin/zram03.
-Mike
Greetings,
Running ltp zram testcases, met the below.
[ 1347.685763] loop: module loaded
[ 1347.809396] zram: Added device: zram0
[ 1347.813256] zram: Added device: zram1
[ 1347.817100] zram: Added device: zram2
[ 1347.820941] zram: Added device: zram3
[ 1347.846747] zram0: detected capacity chan
7 matches
Mail list logo